Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Everything posted by chon_

  1. hmmm.... I remember having trouble with this too, problem was solved rearranging the install order of the hotfixes, I install Update Rollup and Hotfixes via SvcPack.inf. It will be helpful if you give us more details, such as at what stage you're trying to install it, etc. Interesting, never tried installing it via cmdlines.txt, I might give it a try
  2. Well it seems this thread got a little complicated where it should be very very simple. The one and ONLY thing you have to do is add a line to your RunOnceEx.cmd file, How complicated is that? REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /f That's it! @Yzöwl Te above line does work, (tested in 7 PCs and lots and l,ots of vmwares by now hehe ), yours should do it too, only difference is entering the number in decimal or HEX, so as you can see they're the same thing Anyway, I'll test it again with both sintaxes and I'll post my results, although I'm almost sure it works with both of them. @just_laze You are free to use your method if it worked, i'm sure it took a lot of time and testing, we appreciate that. If it suits your needs it's very welcome, i'm sure a lot of people will be using it. As for IE7 taking 15 min to install, that is not entirely true, it takes 1-2 maybe 3 minutes at most including its hotfixes. But personally I just prefer to add a simple line of code instead of use nLite, open hotfixes, add/replace files with older ones, run a batch to copy a file and register a dll, and so on. I'm just too lazy for that Again, I'm glad you have a working method, actually I may give it a try. @everybody Everyone can use whatever they want to accomplish this task, I just found a working method to do it and I wanted tho share it with this forum in a little return of what I've learned from it.
  3. Have you read This thread? Tested several times
  4. Well, I have to admit it, I too was very surprised when it worked. BTW, I forgot to mention that the solution was based in this article too, as you can see near the bottom it says: And that's exactly what that new line of code does (it sets the No Status Dialog Option). Based on that I started to do some testing, and..... these are my results. Give it a try, you have nothing to loose!
  5. Well, I finally made it! Here's what I wanted to do: 1) Install Internet Explorer 7 via RunOnceEx. 2) Reboot. 3) Install IE's hotfixes via RunOnceEx too. 4) Do NOT altere/replace any DLLs and/or other files during the process. Problem is (as you should know by now), that IE7 setup process "clears" RunOnceEx registry key, hence no entries after IE7's setup entry are processed and RunOnceEx entries are not performed on next reboot. Actually the solution is very simple, and it's based in THIS MS article. You just need to add a FLAG to your RunOnceEx key. Below you'll find part of my RunOnceEx.cmd file to illustrate this: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Instalando aplicaciones y mejoras" /f REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /f REG ADD %KEY%80 /VE /D "Adobe Reader 8.0.0" /f REG ADD %KEY%80 /V 1 /D "%CDROM%\install\AdobRdr8\AcroRead.msi /qb" /f REG ADD %KEY%\100 /VE /D "Adobe Flash Player 9" /f REG ADD %KEY%\100 /V 1 /D "%CDROM%\Install\AdobeFlash\install_flash_player_active_x.msi /qb REBOOT=Suppress" REG ADD %KEY%\220 /VE /D "MS Office Professional 2003 SP2" /f REG ADD %KEY%\220 /V 1 /D "%CDROM%\Install\Off_2003\setup.exe TRANSFORMS=Unat.MST /qb-" /f REG ADD %KEY%\230 /VE /D "Internet Explorer 7.0" /f REG ADD %KEY%\230 /V 1 /D "regedit /s %CDROM%\Install\Scripts\TwksXP_u.REG" /f REG ADD %KEY%\230 /V 2 /D "%CDROM%\Install\Scripts\CleanXP.cmd" /f REG ADD %KEY%\230 /V 3 /D "%CDROM%\Install\IE7\IE7-WindowsXP-x86-esn.exe /quiet /passive /update-no /no-default /norestart" /f REG ADD %KEY%\230 /V 4 /D "%CDROM%\Install\Scripts\IE7_Hotfixes.cmd" /f EXIT Note the third line of code: REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /f. This is the only change you should make tou your file to get the work done. This flag prevents RunOnceEx key to be cleared. What IE7_Hotfixes.cmd does, is add registry entries for the hotfixes, which will be installed on the next reboot and restarts the computer after installing IE7. Here's my IE7_Hotfixes.cmd file: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /f REG ADD %KEY%\910 /V 1 /D "%CDROM%\Install\IE7\Hotfixes\IE7-KB929969-WindowsXP-x86-esn.exe /q /n /z" /f REG ADD %KEY%\910 /V 2 /D "%CDROM%\Install\IE7\Hotfixes\IE7-KB928090-WindowsXP-x86-esn.exe /q /n /z" /f shutdown -r -f -t 180 -c "Reiniciando en 3 minutos..." Again, note this line: REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /f. Of course, I use Spanish language, but the same apllies to your language distribution. B) Let me know any comments/doubts.
  6. Anyone succeeded on this? i can't get it to work :-(
  7. Try: [WindowsFirewall] Profiles = WindowsFirewall.TurnOffFirewall [WindowsFirewall.TurnOffFirewall] Mode = 0 in Winnt.sif
  8. Try installing the hotfixes in the folowing order, it works very good for me. This is my svcpack.inf [CatalogHeader] [Version] BuildNumber=2195 MinorVersion=0 MajorVersion=5 Signature="$WINDOWS NT$" [SetupData] CatalogSubDir="\I386\svcpack" [SetupHotfixesToRun] KB890830.exe /q DX9Win2k.EXE IE6Win2K.EXE MPLAYER9.exe /Q:U /R:N "ESN_Q832483_MDAC_x86.EXE /C:""dahotfix.exe /q /n"" /q:a" WUAgent.exe /wuforce /quiet /norestart WindowsInstaller-KB893803-v2-x86.exe /q /n /z WindowsMedia-Q828026-x86-ESN.exe /q /n /z WindowsMedia-KB911564-x86-ESN.exe /q /n /z WindowsMedia6-KB925398-x86-ESN.exe /q /n /z WindowsMedia9-KB917734-x86-ESN.exe /q /n /z IE6.0sp1-KB905495-Windows2000-x86-ESN.exe /q /n /z OE6.0sp1-KB923694-Windows2000-x86-ESN.exe /q /n /z IE6.0sp1-KB925454-Windows2000-x86-ESN.exe /q /n /z IE6.0sp1-KB929969-Windows2000-x86-ESN.exe /q /n /z Windows-KB870669-x86-ENU.exe /Q:A /R:N Windows2000-KB329115-x86-ESN.exe /q /n /z Windows2000-KB842773-x86-ESN.EXE /q /n /z Windows2000-KB891861-v2-x86-ESN.EXE /q /n /z Windows2000-KB893756-x86-ESN.EXE /q /n /z Windows2000-KB896358-x86-ESN.EXE /q /n /z Windows2000-KB896422-x86-ESN.EXE /q /n /z Windows2000-KB896423-x86-ESN.EXE /q /n /z Windows2000-KB896424-x86-ESN.EXE /q /n /z Windows2000-KB899587-x86-ESN.EXE /q /n /z Windows2000-KB899589-x86-ESN.EXE /q /n /z Windows2000-KB900725-x86-ESN.EXE /q /n /z Windows2000-KB901017-x86-ESN.EXE /q /n /z Windows2000-KB901214-x86-ESN.EXE /q /n /z Windows2000-KB905414-x86-ESN.EXE /q /n /z Windows2000-KB905749-x86-ESN.EXE /q /n /z Windows2000-KB908519-x86-ESN.EXE /q /n /z Windows2000-KB908531-v2-x86-ESN.EXE /q /n /z Windows2000-KB911280-v2-x86-ESN.EXE /q /n /z Windows2000-KB912919-x86-ESN.EXE /q /n /z Windows2000-KB913580-x86-ESN.EXE /q /n /z Windows2000-KB914388-x86-ESN.EXE /q /n /z Windows2000-KB914389-x86-ESN.EXE /q /n /z Windows2000-KB917008-x86-ESN.EXE /q /n /z Windows2000-KB917344-56-x86.Exe /Q:A /R:N Windows2000-KB917422-x86-ESN.EXE /q /n /z Windows2000-KB917537-x86-ESN.EXE /q /n /z Windows2000-KB917736-x86-ESN.EXE /q /n /z Windows2000-KB917953-x86-ESN.EXE /q /n /z Windows2000-KB920213-x86-ESN.EXE /q /n /z Windows2000-KB920670-x86-ESN.EXE /q /n /z Windows2000-KB920685-x86-ESN.EXE /q /n /z Windows2000-KB920683-x86-ESN.EXE /q /n /z Windows2000-KB920958-v2-x86-ESN.EXE /q /n /z Windows2000-KB921398-x86-ESN.EXE /q /n /z Windows2000-KB922582-x86-ESN.EXE /q /n /z Windows2000-KB922616-x86-ESN.EXE /q /n /z Windows2000-KB923191-x86-ESN.EXE /q /n /z Windows2000-KB923414-x86-ESN.EXE /q /n /z Windows2000-KB923689-x86-ESN.EXE /q /n /z Windows2000-KB923980-x86-ESN.EXE /q /n /z Windows2000-KB924191-v2-x86-ESN.EXE /q /n /z Windows2000-KB924270-x86-ESN.EXE /q /n /z
  9. Add this code to the very begining oy your CDSHELL.INI: boot: CLS PRINT "\n" PRINT "Press Enter to start from DVD... \n" getkey 6 boot 0x80 IF $lastKey == key[enter]; THEN GOTO menu # When no key found... GOTO bootThis will tell cdshell to wait 6 seconds for the enter key, if the enter key is not pressed, it will boot from hard disk; if pressed it will jump tu the menu section.
  10. @slipk487 If you have a legit XP CD, I can't explain myself how you ended up with no winnt32.exe. Anyway, here's a link for the XP Pro SP2 files
  11. @uid0 That's exactly the "temporary solution" i'm using for now, but I don't like it as a definitive solution, i'll keep trying. Thanks @The008 Interesting! I'll burn a dvd later today and test it. I will also do what mediapla is suggesting. Thanks, to all, i'll let you know how it went!
  12. Hi, I recently started testing "Bootable CD Wizard (BCDW) v2.0a1" for my multiboot DVD (I've always used cdshell), it works great, but I want an option that lets you choose whether to start from cd or not. After a lot of reading, I found that adding the file bootfix.bin from my XP Cd in the BCDW folder will do he trick, but guess what? It doesn't!! it keeps booting from the DVD Am I doing somethin wrong? Any help will be much appreciated
  13. dhdan is coorect. Its th MS Boot Sector of a CD (referred as PRO1.DAT, etc ) in flyakite's guide. Indeed, it should point to a custom folder.
  14. I don't think so. Reason? Because cdshell is not an OS itself, it's only a script debugger.
  15. you can even achieve this with only one floppy bootable image and editing the autoexec.bat file to suit your needs. This seems more simple to me if you're only instaling 95, 98, me.
  16. Hi! Have ytou read this?? Please be more specific, what gives this error? the floppy itself, or CDSHELL? Please comment any other helpful details (like folder structure, autoexec.bat, etc).
  17. Very common issue! Just take it easy, relax! there's nothing you can do (AFAIK)!
  18. As for the Root Certifacate Update, are looking for this file??
  19. Have you tried McAfee Protection Pilot for deploying McAfee? It usually comes with your VirusScan Software. I think it's easier that way.
  20. Francesco is correct, Windows Server 2003 R2 is just a normal Windows Server 2003 SP1 plus a 2nd disc containing the R2 features. just copy the CMPNENTS folder of your windows server Disc 2 to the root of your Windows Server distribution folder, then, in runonceex.cmd call %CDROM%\YourDistributionFoldeHere\CMPNENTS\R2\setup2.exeThis will install R2 features to your existing Win2003 installation.
  21. Could you please be more specific in your error message? in which part of setup pops out? what's exactly the error text? Besides the OS, what else are you installing (drivers, apps,etc)??
  22. @damian666 I'll try to help you to include Win98 to your DVD, please feel free to ask any question if there's something not clearly specified. 1) Create a Windows 98 or Windows ME boot disk. You can do it from within your win98 OS, or you can get an image file from here. 2) Create a Win98 folder within your setup folder, your folder structure should look like this: C:\DVD C:\DVD\SETUP C:\DVD\SETUP\Win98 3) copy the content of your Win98 CD to the C:\DVD\SETUP\Win98 folder (you may remove the "Extras" and "Support" folders. 4) If you have a Win98 boot disk image file (.ima or.img file), skip this step. If not, we assume you've created your Win98 startup diskette. - Please download winimage (shareware). You can download it from here. - Install it. - Insert your win98 startup diskette on your floppy drive - Open Winimage - Click on Disk\Read Disk (or just press Ctrl+R) - Click on File\Save As. Name it Win98.ima (be sure to select "Image file [*.IMA] from the 'Save as' dropdown list. - Voilá! you have your Win98 Boot Image! 5) Copy Win98.ima to a folder of your choice, I personally prefer C:\DVD\Setup\BootSect, but it's up to you, just be sure it's not in the root folder of your project. Now here's the tricky part: * Open Win98.ima file with winimage. * Drag and drop Autoexec.bat file to your desktop. Don't close WinImage!! * Right click Autoexec.bat file (in your desktop), and select Edit. * find the following line (or the most similar) path=%RAMD%:\;a:\;%path%;%CDROM%:\* modify it to include your Win98 source in the path variable: path=%RAMD%:\;a:\;%path%;%CDROM%:\;%CDROM%:\SETUP\Win98\* Below that line type: Setup.exe, your autoexec.bat now should look like this (among other lines of code): echo Loading... echo. path=%RAMD%:\;a:\;%CDROM%:\SETUP\Win98\ Setup.exe echo. GOTO QUIT* Save your autoexec.bat file * Drag it to your WinImage open window, click yes when prompted if you want to overwrite it. * Save your Win98.ima file and close winimage. 6) Now goto C:\DVD\BOOT and open CDShell.ini (we'll be using André Guimarães Casal's file for this example) Add the following line just below the XP Professional one: print "2) Windows 98 \n". Part of your cdshell.ini should now look like this: print c "\n\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ<\c0B$time $date\cXX>ÄÄ \n\n" print c "\cXXMicrosoft Windows XP Professional \n\n" print l "\cXXPress \c0BF1 \cXXfor Help"; print r "\c0Bwww.globalgrooves.pt.vu \n" print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n" print "1) Windows XP Professional \n" print "2) Windows 98 \n" print "\n" print "X) More Options... \n\n"Now go to the getkey part and add: "if $lastKey == key[2]; THEN DISKEMU /Setup/BootSect/Win98.IMA" (without the quotes), be sure to point where your .IMA file resides. Now it should look like this: MainKey: getkey 20 boot 0x80 if $lastKey == key[1]; then goto XP_Pro if $lastKey == key[2]; THEN DISKEMU /Setup/BootSect/Win98.IMA if $lastKey == key[q]; then endSave changes to your cdshell.ini file. Now if you type number 2 key in the cdshell boot menu, cdshell will load win98.ima boot disk, which will run the autoexec.bat file, who is responsible for calling setup.exe from the C:\DVD\SETUP\Win98 folder. Well, that's it, that should do the trick! Of course if you want your win98 setup to be unettended you'll have to deal with the msbatch.inf file. But that would take another tutorial beyond the scope this topic Again: fell free to ask!
  23. OEM software version DO include the repair option, beleive me, I own an OEM company
  24. Hmmmmm Why not just install windows in C: then go to Control Panel\Administrative tools\Computer management\Disk management right click, choose change drive letter. Will that help??
  • Create New...