Jump to content

bryanh

Member
  • Posts

    95
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by bryanh

  1. I don't know what the problem is. I have no problem with this at all. WAIT is looking for your CDFile in the root of each of the drives that windows says is a CD Rom drive. Therefore if you are using a harddrive this will never work. That is what the CDDefault is for. I also test with a harddrive. I have a CDDefault of "j:\o\root". This way %cdrom%\apps\installscripts becomes "J:\o:\root\apps\installscripts" during testing but it's "m:\apps\installscripts" during an install on my current machine. Make sense?
  2. I can add this - but you will run out of screen space very quickly.
  3. So if I understand you would like WAIT to run from cmdlines.txt - make all the settings to RunOnceEX and then exit? Upon reboot RunOnceEx will install the apps. Is that correct? If so then the following would also be true 1) Since WAIT uses RunOnceEx to create a RunOnceEx window for EACH catagory, there would only be one RunOnceEx window (since it's running during reboot and not by WAIT) 2) If this is the case then you would probably want the items in the RunOnceEx window to be the catagories and not each application. This is due to screen size limitation. Is this really what you want to do. I would think that you could enter the correct line to run in WAIT and then have WAIT make the updates to the registry. I already have the code to do that in place (it's used if you use the RunOnceEx option). Therefore there is no need to have a nero.reg file. WAIT would update the registry to run "UA-nero6.exe" on next reboot. If this is all correct than I am sure I can add this will only a little effort. Let me know and I will look into it. Bryan
  4. Numéro 1 ! You are a King! Now i can use Wait , without crash Thx alots Bryanh <{POST_SNAPBACK}> Gald it works (and even happier to have solved the bug). Thanks for your help Bryan
  5. Okay - here is some information %cdrom% is determined by looking at all CD Drives in the system. For each CD Drive is looks for ALLDVD.TXT in the root. If the file is found then that is what %cdrom% becomes. My default %cdrom% is "J:\o:\root". I use this for testing as I don't want to burn a DVD/CD for each test. Therefore, you are getting "j:\o\root" beacuse WAIT cannot find "AllDVD.TXT" in the root of any of your CD drives. **** SOLUTION *** The next version (0.09)- which will be posted today with have two new settings (amongst other things) 1) CDFILE - you set this to the file that WAIT should look for in the root of your CD drives. If found then %cdrom% will be set to that drive 2) CDDefault - you can set this to whatever path you like. If WAIT cannot find the CDFILE then %cdrom% will be set to CDDefault. Hopefully this will solve the %cdrom% problem Bryan
  6. You can accomplish EXACTLY what you want with the following information under [unattended] in your winnt.sif file. Repartition=No Specifies whether to delete all partitions on the first drive of the client computer and to reformat the drive with the NTFS file system automatically. FileSystem=* If you prefer to manually choose a partition during text-mode setup with full control on choice of filesystem, add this entry to your winnt.sif file. I do this for my installs. The only question I have to answer is what partition to put the install in, and what file system I want. After that it's all unattended. Then I use WAIT (see my sig below) to select which applications I want installed.
  7. How about a setting in the ini file for the size of each column?
  8. Here is just a suggestion (and of course it will cause a bunch of replies). I use AutoIt3 for ALL my installs. I wrote an AutoIt script for each install process. The last part of the AutoIt scripts does the following 1) Removes any ICONS on both the "Admin" and the "All Users" desktop 2) Moves ANY program groups from "Admin" to "All Users" (this way all uses have access to the program) 3) SOME installs move the program groups into groupings. For example all my DVD Tools are moved into a "DVD Tools" group on my start bar. Learning AutoIt is VERY easy. Once you write a couple it very quick.
  9. I THINK the crash is fixed in version .08. Please check it when you get a chance and post your results Thank you
  10. Funny you should ask - here is a few lines from my exact regtweak.cmd (yes it's a cmd file since you are running "reg" set DEFAULT_USER=%ALLUSERSPROFILE%\..\Default User set KEY=HKU\XPTWEAK reg load %KEY% "%DEFAULT_USER%\NTUSER.DAT" call :RUN_REGTWEAKS reg unload HKU\XPTWEAK set KEY=HKCU call :RUN_REGTWEAKS goto :EOF :RUN_REGTWEAKS REM Prevents Internet Explorer windows from being reused reg add "%KEY%\Software\Microsoft\Internet Explorer\Main" /V AllowWindowReuse /t REG_DWORD /d 00000000 /f
  11. I have no idea. I do not have this problem and it would seem that no one else does either. I will see if I can add some stack trace code. If so, it will create a text file if the program crashes. If you send me the file I can (hoepfully) trace where the program crashed. I will see if I can add it in the next version. it's MFC and that stands for "Microsoft foundation classes". It's the class library that comes with MS VC++
  12. Yup - I fully understand what you are saying. I have solved the problem you described as follows. 1) reg /load XPTWEAKS %ALLUSERSPROFILE%\..\Default User\NTUSER.dat 2) change all [HKEY_CURRENT_USER\... to [HKEY_USERS\XPTWEAKS\... 3) run all your reg updates 4) reg /unload XPTWEAKS This will set the reg settings to the default user. Every new user you create will have these setting as defaults now.
  13. CMD=regedit /s %cdrom%\apps\regfiles\file.reg correct It looks for ALLDVD.TXT in the root directory currently you cannot - I will add code to handle this. How about %LB% (for line break)? This is not a bug as much as running out of room on the screen. There is a limit to the amount of text that can be displayed for each checkbox. There is really no solution to this problem. I can only allow so much space. Suggestions?
  14. Will be corrected in the next version correct I am not sure about "compared to wpi" but on my machine the CPU is at 1% during install from WAIT This "problem" will not exist in WAIT. You do not need the reg file either. I will look into a background picture.
  15. and it did not work? BD <{POST_SNAPBACK}> Fixed and new version posted.
  16. I am bias, but you might want to check out WAIT. W.A.I.T (windows application installation tool)
  17. Updated the post with an new version. Please check the CPU usage and the "crash". I cannot reproduce this crash so let me know.
  18. I have confirmed this problem - and fixed it. I am moving the custom buttons as requested in another post and will update the download in about 10 minutes. Bryan
  19. No, I am saying that it should not work that way, not that the problem is only yours. I will run an install and look at the task manager. I will let you know the results.
  20. Are you saying that during install the programs are run in groups of 5? But only when using button1? There is no connection between the custom buttons and the actual install so I am unsure of the problem. The buttons set checkboxes. This is strange. I do all my testing with my real CFG file and it has words for ALL the UIDS. Perhaps there is an issue with "spaces" in the UID as I don't have any. I will look into this.
  21. Unlimited CMD lines is already supported (since the very first version). Just add more CMD= lines. They will run in order. Bryan
  22. Already fully supported. Just add more CMD= lines. They are run in the order that they are in the file. Not sure what you mean about this one. The cat's are determined by the cat's for each program. Can you explain more? No problem - next version You're quite welcome Personally I have no need for a background, but if there is enough interest I will look into it.
×
×
  • Create New...