Jump to content

gospeed

Member
  • Posts

    103
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    United States

Everything posted by gospeed

  1. I was previously using an older method (before the .exe was released) of running wpi.hta during the first boot, but it was interfering with my driverpacks finisher. I have a "wpi" folder at the root of my dvd, with all the wpi stuff inside it to keep it all clean. Here is my old modified .cmd: for /f "delims=: tokens=1" %%i in ("%~dp0") do set drive=%%i: set wpipath=%drive%\wpi SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\999 /V 1 /D "%wpipath%\WPI.hta" /f How do I go about modifying the new .inf to point to the correct file? I am not sure about the language that I can use in this .inf file [Version] Signature="$CHICAGO$" [DefaultInstall] AddReg=Run.AddReg [Run.AddReg] HKLM,"%RUN%","%WPI%",,"RunDll32 advpack.dll,LaunchINFSection ""%01%\%INF%"",Execute" [Execute] RunPreSetupCommands=Launch.WPI:1 DelReg =Run.DelReg [Launch.WPI] CMD /Q /C CD /D """%01%\..\WPI""" & START /WAIT /B WPI.hta [Run.DelReg] HKLM,"%RUN%","%WPI%" [Strings] RUN="SOFTWARE\Microsoft\Windows\CurrentVersion\RUN" WPI="Windows Post Install" INF="RunWPI.inf" Thanks in advance!
  2. After using the Vista Anytime DVD, I like how, by typing in your key, IT chooses which version to install. Has anyone developed a way, where inside the boot menu, you could type in your key and it would decide which version, and chain it? I am not sure how that would work with the winnt.sif, it would be nice to only type the key once. I have searched and cannot find anyone that has done this.
  3. Thank you kof94 and Siginet! Siginet, I have looked at powerpacker but was under the assumption that I could only have one instance of xp running various winnt.sif's, however it sounds as if that is not true. I will do some looking! If I could chop out 2/3's I would be SO HAPPY! 54/3= 18 Now I need to start remembering all the stuff I forgot over the last year while I was being complacent with what I had
  4. Here is a run down of my dvd. I have Retail versions of XP Home, Pro, Student, and MCE- and 3 install types for each (Attended, Unattended, and original) I then have 7 OEM XP installs for Home and 7 for Pro, again with 3 install types. So 54 total folders (besides my boot folders) for 54 different versions. When combined with my .bin files, boot folders, boot menu, and wpi stuff, I have 136 items at the root of my dvd Its a MESS! I used both the gosh method and the flyakite tutorial to build this dvd, which originally just had 9 installs. Its now 9.95gb before running CDimage, only 3.29gb after. Most of that is my WPI programs. My thought is that since there are only a handful of files different between most versions of XP, and 2/3 of mine ONLY differ in the winnt.sif file, there HAS to be a better (more efficient way!) to do this! Are there any methods to building a multiboot that do not require the repetition? It would be nice to have 3 different winnt.sif files in the same folder and change how they are called. It would also be nice to have only one instance of a file anywhere on the dvd. I know its likely not possible, but if someone is doing this, or at least a more efficient method than mine, please chime in! I am at the point that I need to update my DVD anyway, so I am up for trying something new.
  5. Well, I played with bcdw a bit and really like it, and it seems to be stable on all my machines which cdshell was not. I will likely get into isolinux at some point, but for now this will work just fine! thanks everyone B) And in response to the end of bcdw, what is it with all the great people in our hobby just disappearing? Poof! Gone .
  6. Thanks for the quick advise, checking out BCDW right now...
  7. Completely FED UP with CdShell and its errors. Tried different brands of disk, different drives, and different pc's. CdShell boots up about once out of 10 times, when its in the mood. The other times it gives and error with a code that apparently has not been decoded, as a google search only finds more problems like mine. I could deal with it if it wasnt so intermittent. I need something RELIABLE! I am not familiar with any boot menu's besides cdshell and bootscriptor, and I am trying to find something that is similar (Easy to learn!), yet current and supported. Can I get some recommendations? Again, ease of use for me is most helpful. Maybe someone has a sample of their boot menu I could take a look at to see how its set up? I like how easy to understand both cdshell and bootscriptor were. Thank you in advance! ----Jeff
  8. ah, ok. I have searched before and it seemed inconclusive if dell had a volume key for MCE. Thanks for the info.
  9. anyone know if Dell's Media Center Edition uses a volume key like Pro and Home? I have yet to find a machine to Jellybean and compare.
  10. Personally I use a key to help me keep them all straight. I know in Gosh's method, she renames the Install folder "XPhome" and such, but leaves the boot folders 4 capital letters. I think this is because of the need to hex edit, but I am by no means an expert. Since my CD follows Gosh's method, I stuck with it and just make all my folders 4 letters. Here is my key that I use: First Second Third Fourth ----------------------------------------------------------------------------------------------- A=ATTENDED P=BOOT FOLDER P=PRO R=RETAIL U=UNATTENDED B=INSTALL FOLDER H=HOME O=OEM X=ORIGINAL M=MCE C=CORPORATE So, for example, my Unattended XP Home OEM folder is called "UPHO"
  11. Maybe your keyboard is faulty. Have you tried a known working one? lol, yeah, I am typing on it now . My test PC is hooked up with a KVM switch so I am using the same keyboard, mouse, and monitor for both. Its really just confusing me...i have tried other boot menu's, both Bscript and diskemu, they both work 100% of the time....
  12. works perfectly now, thank you so much! No more blank screen This really shouldnt even be an option though, progress bars are 110% necessary!
  13. I rewrote the press any key part a few times, tried the ideas mentioned here, and it still is intermittent. I just tried to get it to load and after the 6th reboot it took.
  14. Yes to all My Presetup wording is exactly that...it was only modified to add your line to it my OEM folder is in the root...there is only one OEM folder but 6 O/S's that point to it I performed the batch file within my OEM folder, and it seems to have created and edited just as designed- and then I deleted the .7z driverpacks. Here is my presetup.cmd Thanks for taking a look! REM +==========================================================================+ REM | | REM | This presetup.cmd file was dynamically generated by the DriverPacks | REM | BASE, to work with the DriverPacks without any further editing. | REM | However, if you would like to add some custom functionality, you can | REM | edit this file without any problems. Just take into record that this | REM | file will be erased if you run the DriverPacks BASE on these Windows | REM | installation files again! | REM | | REM | With special thanks to: | REM | -Pyron, a06lp and iLE for their help with this method; | REM | -schalti for the optional 'Keep the Drivers' system and Pyron (again) | REM | for turning it into an executable. | REM | | REM +==========================================================================+ REM +==========================================================================+ REM | Showing the progress bar | REM |--------------------------------------------------------------------------| FOR %%h IN (%CDDRIVE%\OEM\DP*.exe) DO "%%h" x -y -aoa -o"%SystemDrive%" REM +==========================================================================+ REM | Finding CD/DVD driveletter. | REM |--------------------------------------------------------------------------| SET TAGFILE=\OEM FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i: REM +==========================================================================+ REM | Decompressing the DriverPacks to the harddisk. | REM |--------------------------------------------------------------------------| %CDDRIVE%\OEM\bin\7z.exe x -y -aoa %CDDRIVE%\OEM\DP*.7z -o"%SystemDrive%" REM +==========================================================================+ REM | Copying/decompressing the files to finish the installation. | REM |--------------------------------------------------------------------------| %CDDRIVE%\OEM\bin\7z.exe x -y -aoa %CDDRIVE%\OEM\bin\DPsFnshr.7z -o"%SystemDrive%" COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\ IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%\ REM +==========================================================================+ REM | Scanning for driverdirectories. | REM |--------------------------------------------------------------------------| %CDDRIVE%\OEM\bin\DevPath.exe %SystemDrive%\D REM +==========================================================================+ REM | Disable Driver Signing Policy and keep it disabled. | REM |--------------------------------------------------------------------------| START %SystemDrive%\DSPdsblr.exe EXIT
  15. Well, I guess I should ask, what method if driverpack install is this meant for? I used BTS driverpacks, and used driverpacks base to install them into each of my individual O/S's. I am using the method #2 where they create a fake setup that is executed before actual setup. My DVD works fine as it sits, but I notice that your folder structure is different than mine (your driver pack sits in OEM\Drivers, where mine is directly in OEM) and I am not sure if that makes a difference. I did modify the command to delete the _ and also edited my presetup.cmd to delete the _ and change the folder structure (deleted \Drivers). It skips right over where the drivers once were being installed, like it cant find the files. Is there any problem with the folder structure being different? This is the contents of my OEM folder: BIN ATICCP.INS DPC6091.7Z DPCP6091.7Z DPGA6011.7Z etc... There is no driver folder inside.
  16. I just changed the first part to this: boot: cls set textColor= color[white on black] set boldColor= color[cyan on black] cls print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\cXXSpeedCD9\n\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press Enter to install Windows XP... \n" getkey 10 boot 0x80 if $lastKey == key[enter]; then goto menu # When no key found... boot 0x80 And it made no difference. Still didnt pick up until the third time I rebooted.
  17. I will post my .ini below, but I dont think it is the issue. It works- most of the time...splash screen comes up, then the "press any key.." part. Most of the time it loads up the correct OS and its good to go. But sometimes it wont respond to a keystroke- and will continue like you never tried to press anything. This is on the same machine within 5 minutes! If I restart, every few times it will pick up. I am not using a USB keyboard if that makes a difference. edit... Once it enters the setup, keystrokes are always found. It never acts buggy except when trying to catch the "press any key.." part Anyway, here is my .ini: boot: cls set textColor= color[white on black] set boldColor= color[cyan on black] cls print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\cXXSpeedCD9\n\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press any key to install Windows XP... \n" getkey 10 boot 0x80 # Printing the Interface goto menu menu: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXSpeedCD9\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n" print c "\n" print " Press 1 to Install Windows XP Professional\n" print " Press 2 to Install Windows XP Home\n" print " Press 3 to Install Windows XP Media Center\n" print c "\n" print " Press Q to Quit to Command Prompt \n" print " Press R to Reboot \n" print c "\n" MainKey: getkey 20 boot 0x80 if $lastKey == key[1]; then goto XP_Pro if $lastKey == key[2]; then goto XP_Home if $lastKey == key[3]; then goto MCE_R if $lastKey == key[q]; then end if $lastKey == key[r]; then reboot if $lastKey == key[esc]; then boot 0x80 Help: cls print c "\n\cXXSpeedCD9 Help \n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print " Special Thanks to Gosh, Flyakite, Jaws75, Alanoll, and everyone that has \n" print " helped me and led me along the way. I am not the Pioneer, they were. \n" Print c "\n\n" print " Retail versions of XP require a valid key and will need to be activated \n" print " OEM versions of XP are for OEM product Keys only\n" print " Corporate Edition is only for Corporate or Student Keys \n" Print c "\n\n" print " There are 3 sub-options for each version of XP. Choosing 1 will ask \n" print " for your input while Windows is being installed. Choosing 2 will \n" print " automatically fill in the info, but will allow you to alter it. \n" print " Choosing 3 will only ask you for the product key \n" Print c "\n\n" Print c "\n\n" print "Press any other key to return to main menu... \n" getkey goto menu XP_Pro: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXMicrosoft Windows XP Professional\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press 1 for XP Professional Retail Version \n" print " Press 2 for XP Professional OEM Version \n" print " Press 3 for XP Professional Corporate Edition\n" print c "\n" print " Press any other key to return to main menu... \n" XP_Pro_Key: getkey 20 goto menu if $lastKey == key[1]; then goto PRO_R if $lastKey == key[2]; then goto PRO_O if $lastKey == key[3]; then goto PRO_C if $lastKey == key[F1]; then goto Help goto menu PRO_R: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXMicrosoft Windows XP Professional Retail Version\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press 1 If you want to supply your own settings\n" print " Press 2 If you want SpeedCD to provide recomendations\n" print " Press 3 If you want SpeedCD to do all the work for you\n" print c "\n" print " Press any other key to return to main menu... \n" PRO_R_key: getkey 20 goto menu if $lastKey == key[1]; then chain /XPPR.DAT if $lastKey == key[2]; then chain /APPR.DAT if $lastKey == key[3]; then chain /UPPR.DAT if $lastKey == key[F1]; then goto Help goto menu PRO_O: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXMicrosoft Windows XP Professional OEM Version\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press 1 If you want to supply your own settings\n" print " Press 2 If you want SpeedCD to provide recomendations\n" print " Press 3 If you want SpeedCD to do all the work for you\n" print c "\n" print " Press any other key to return to main menu... \n" PRO_O_key: getkey 20 goto menu if $lastKey == key[1]; then chain /XPPO.DAT if $lastKey == key[2]; then chain /APPO.DAT if $lastKey == key[3]; then chain /UPPO.DAT if $lastKey == key[F1]; then goto Help goto menu PRO_C: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXMicrosoft Windows XP Professional Corporate Edition\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press 1 If you want to supply your own settings\n" print " Press 2 If you want SpeedCD to provide recomendations\n" print " Press 3 If you want SpeedCD to do all the work for you\n" print c "\n" print " Press any other key to return to main menu... \n" PRO_C_key: getkey 20 goto menu if $lastKey == key[1]; then chain /XPPC.DAT if $lastKey == key[2]; then chain /APPC.DAT if $lastKey == key[3]; then chain /UPPC.DAT if $lastKey == key[F1]; then goto Help goto menu XP_Home: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXMicrosoft Windows XP Home\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press 1 for XP Home Retail Version \n" print " Press 2 for XP Home OEM Version \n" print c "\n" print " Press any other key to return to main menu... \n" XP_Pro_Key: getkey 20 goto menu if $lastKey == key[1]; then goto HOME_R if $lastKey == key[2]; then goto HOME_O if $lastKey == key[F1]; then goto Help goto menu HOME_R: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXMicrosoft Windows XP Home Retail Version\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press 1 If you want to supply your own settings\n" print " Press 2 If you want SpeedCD to provide recomendations\n" print " Press 3 If you want SpeedCD to do all the work for you\n" print c "\n" print " Press any other key to return to main menu... \n" HOME_R_key: getkey 20 goto menu if $lastKey == key[1]; then chain /XPHR.DAT if $lastKey == key[2]; then chain /APHR.DAT if $lastKey == key[3]; then chain /UPHR.DAT if $lastKey == key[F1]; then goto Help goto menu HOME_O: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXMicrosoft Windows XP Home OEM Version\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press 1 If you want to supply your own settings\n" print " Press 2 If you want SpeedCD to provide recomendations\n" print " Press 3 If you want SpeedCD to do all the work for you\n" print c "\n" print " Press any other key to return to main menu... \n" HOME_O_key: getkey 20 goto menu if $lastKey == key[1]; then chain /XPHO.DAT if $lastKey == key[2]; then chain /APHO.DAT if $lastKey == key[3]; then chain /UPHO.DAT if $lastKey == key[F1]; then goto Help goto menu MCE_R: cls set textColor= color[white on black] set boldColor= color[cyan on black] print l "\n\cXXPress \c0BESC \cXXto Exit"; print r "\cXXPress \c0BF1 \cXXfor Help \n" print c "\n" print c "\cXXMicrosoft Windows XP Media Center Edition\n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print c "\n\n" print " Press 1 If you want to supply your own settings\n" print " Press 2 If you want SpeedCD to provide recomendations\n" print " Press 3 If you want SpeedCD to do all the work for you\n" print c "\n" print " Press any other key to return to main menu... \n" MCE_R_key: getkey 20 goto menu if $lastKey == key[1]; then chain /XPMR.DAT if $lastKey == key[2]; then chain /APMR.DAT if $lastKey == key[3]; then chain /UPMR.DAT if $lastKey == key[F1]; then goto Help goto menu end
  18. WOW! now that is fast service! I will give it a shot here in just a sec. Thanks!
  19. Any way around this? My driver packs were renamed along the way (for example, DPGC609.7Z) and since its a multiboot with quite a few O/S's on it sharing the one OEM file, it would take some work to rename them. I am not quite sure when they got renamed along the way but if they can be changed back I would need to know what documents reference to them to change the wording back I guess. I looked in presetup.cmd, but it doesnt appear to be referencing them by their names specifically? Is it really just as simple as renaming them back? Wish I would have read about this method before I started! Progress bars would rock! Thanks in advance! ----Jeff
  20. I destroyed the old autorun because I want to both conserve disks and make it dual purpose as well. I never load windows from the desktop, so its nice to just plunk in the disk and have WPI pop up. I am going to try changing the autorun to use the ShellExecute and see what happens. Oh, thats not a bad idea either....hmmm Thanks guys for the quick responses. UPDATE: ShellExecute worked perfectly...I just didnt know that command:) I was definately doing it the hard way but that seems to be how I learn
  21. well, after doing a full reinstall on my test pc, it now works 100% of the time. If I insert the dvd, it starts WPI, if I click on the drive icon, it starts WPI. But on any other pc that the disk has not been installed on it seems to not want to find the correct drive silently. Any thoughts? Its obviously not a wpi problem, but I figure others out there have done this same thing so maybe they have ideas or another way of "finding" a cdrom.
  22. On my setup, the cmdlines.txt and the RunWPI.cmd both sit inside the $oem$ folder. cmdlines is what calls the RunWPI.
  23. Ok, so my unattended DVD works great, and it calls WPI which works great as well. So I decided that when I insert my unattended DVD (since I dont ever install XP from a Windows environment) I want it to start up WPI. So I took out the Autorun file that was there and rewrote it to run wpi instead: [AutoRun] open=wpistart.cmd icon=speed.ico It calls my Icon and Starts a short script I wrote that should start the WPI.hta ECHO off if exist d:\wpi set cdrom=d: if exist e:\wpi set cdrom=e: if exist f:\wpi set cdrom=f: if exist g:\wpi set cdrom=g: if exist h:\wpi set cdrom=h: if exist i:\wpi set cdrom=i: if exist j:\wpi set cdrom=j: if exist k:\wpi set cdrom=k: if exist l:\wpi set cdrom=l: if exist m:\wpi set cdrom=m: if exist n:\wpi set cdrom=n: if exist o:\wpi set cdrom=o: ECHO. ECHO off %CDROM%\wpi\WPI.hta But when it runs, it comes up with a box that states "Windows- No Disk" "There is no disk in the drive" "please insert a disk in the drive". When you click cancel a few times, it will finally find the correct cdrom and start WPI. In samples where my cdrom is drive H:, it takes a few clicks. In samples where my cdrom is drive d: it goes right in. From there out we are all good. Any ideas why my method of finding the correct cd drive is not working silently? I have seen it used many many times before, but it seems that it cant progress to the next line without giving me an error first.
  24. Edit...think I figured it out...the search function took some "creative wording" to find what I was looking for! I ended up placing all these tweaks in my C:\test3\$OEM$\$1\Install folder and called it in my C:\test3\$OEM$\$$\source.bat folder- seems to work great, all the tweaks do what they are supposed to. Anyone have a tweak to remove the sample files, like the My Music folder and the My Pictures? Maybe I missed it but I have tried! thanks all for the help---Jeff
  25. I have gotten pretty far with making my own unattended CD including tons of stuff I have read about on this site, but now I am stumped! I have searched quite a bit here and I cant seem to find the answer. I have all these reg tweaks that I want to use saved as "setup.reg" and saved in my C:\test\$OEM$\$1\Install folder along with my other programs that are installing correctly. I have actually tried it in a few different folders from what I gathered from posts here and other websites, but I have never seen anyone explain where this is supposed to reside? I have installed quite a few features into my xp install disk so far, but this has me stumped! Thanks in advance, you guys are awesome. I named it .txt just to post it here, it is .reg (disabled "hide extensions" after my last problem;) within my folder. setup.txt


×
×
  • Create New...