Jump to content

Alanoll

Patron
  • Posts

    5,494
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Alanoll

  1. if CD.TXT is in the root of your driver, CDROM returns just the drive letter, so the SOFTWARE dir could be placed at the root of your structure. Otherwise all your paths will be %CDROM%\SETUP\XPVOL\SOFTWARE or something along those lines.
  2. just glancing through, you did wait untill the Desktop loads right? As that would be when RunOnceEX runs, unless you include the command for it to start..... continueing to glance through... Your Metapad entries aren't correct. REG ADD %KEY%\015 /VE /D "Metapad 3.5." /f REG ADD %KEY%\015 /V 1 /D "%CDROM%\Software\metapad" "%systemdrive%\WINDOWS\" Won't work. I'm guessing your copying files? You should use CMD.exe /C or just put the copy command in a seperate batch file to call. The batch file would be easier as you won't have to include embedded quotes. What you could use it something like.... REG ADD %KEY%\015 /VE /D "Metapad 3.5." /f REG ADD %KEY%\015 /V 1 /D "%CDROM%\Software\METAPAD.CMD %CDROM%" /f and in METAPAD.CMD copy %1\Software\Metapad %systemdrive%\Windows REG ADD %KEY%\016 /VE /D "Metapad 3.5 Filters" /f REG ADD %KEY%\016 /V 1 /D REGEDIT /S "%CDROM%\Software\metapad\filters.reg" /f should be REG ADD %KEY%\016 /VE /D "Metapad 3.5 Filters" /f REG ADD %KEY%\016 /V 1 /D "REGEDIT /S "%CDROM%\Software\metapad\filters.reg" /f REG ADD %KEY%\035 /VE /D ".NET Framework v1.1" /f REG ADD %KEY%\035 /V 1 /D "%CDROM%\Software\NetFramework\netfx.msi /qb /f should be REG ADD %KEY%\035 /VE /D ".NET Framework v1.1" /f REG ADD %KEY%\035 /V 1 /D "%CDROM%\Software\NetFramework\netfx.msi /qb" /f REG ADD %KEY%\040 /VE /D "Office XP Professional with Frontpage" REG ADD %KEY%\040 /V 1 /D "%CDROM%\Software\OfficeXP\setup.exe TRANSFORMS=%systemdrive%\install\Applications\OfficeXP\Unattended.MST /qb" /f should probally be REG ADD %KEY%\040 /VE /D "Office XP Professional with Frontpage" REG ADD %KEY%\040 /V 1 /D "%CDROM%\Software\OfficeXP\setup.exe TRANSFORMS=%CDROM%\Software\OfficeXP\Unattended.MST /qb" /f As for it not running, evertying looks right, unless it's these syntax errors and you're not waiting for the desktop to load. RunOnceEX loads the restart AFTER the keys are imported, so importing at CMDLINES.TXT would mean they're executed at GUIRunOnce point (when the actual desktop loads, after the user logs in)
  3. Please use code tags when posting code.....
  4. Man, I must have a machine better then best, I play Halo while it goes. lol. I switch back and forth, and in about 10-15 minutes, the cabs are done, and Halo didn't slow down.
  5. if you had another computer that had a burner, just rip your CD to it, delete the WINNT.SIF file, and you're off. But then it won't be unattended
  6. oooh yes..... XPlode was created. Nice little program to replace RunOnceEX and Command prompt.....uses XML files, and you can customize the display with graphics and what not. XPCreate has gone basic, no more GreenMenu, and I think works a bit better. Multiboot guides Seperate Driver forums. RAID/ATA driver slipstreaming A newly esigned Unattended Site. Alot has changed, but I think you'll be pleasantly surprised that alot of the old people still stop in once in awhile.
  7. are all the slipstreaming performed by SVCPACK.INF or CMDLINES>TXT? Not using GUIRunOnce at all? If so, it should still be possible. Use a Win98 startup disk, emulated or otherwise, and navigate to your CDROM, then CD \I386 winnt.exe I believe that should start a normal attended installed, but the hotfixes and whatnot should still be there, assuming you had everything run from CD (the hotfixes should if you sed SVCPACK.INF). If anything was copied over to the harddrive, it won't work unless you copy it before setup starts by your self.
  8. oh, it gets confusing sometimes, especially with all the different names. Some call it Windows Update method (like in this thread) others RunOnceEX, others just plain RunOnce (there are quite a few different RunOnce methods) and then those who just followed what they saw without knowing what it was. As a side note, I beleive Aaron based the guide from one of your posts awhile back. After this one was created, you made a seperate thread. Ah yes, here it is.... http://www.msfn.org/board/index.php?showtopic=9753 The difference being yours uses REG files, where as Aaron's uses the REG.EXE command in a batch file so that variables can be used without problems and variables for CDroms can be declared and also used. It's good to have you back nonthe less. It's been a long time.
  9. where is Chris's guide? I knwo of this one... http://unattended.msfn.org/xp/runonceex.htm and this one: http://unattended.msfn.org/xp/runonceex_cd.htm and there are a few posts I've seen in the forum..... Perhaps explaining a bit better of what you've done?
  10. then it is RunOnceEX. Atleast puroosing through your site looks like. http://unattended.msfn.org/xp/runonceex.htm Look similar? Do Correct Me if I'm wrong. I'm always open to new ways of doing the same thing
  11. you have of course gotten a copy of RyanVM's lated build of drivers from 5/20? Always a good place to start.
  12. using a Winnt.sif file? Setup has problems with using both Winnt.sif and RAID driver from floppy. What you could do, is remove the floppy all together and add the driver to the CD.
  13. I believe this is just the RunOnceEX method correct? Windows Update = RunOnceEX? Or is it using the RunOnce\Setup Key? If it's RunOnceEX, there is a guide to it on the unattended website, as well as running stuff from the CD using it. It uses batch files, but it does get aroudn teh annoying variable problem.
  14. so you want to go on stike do ya? well when I get home later, I'll compare file versions with what I have, and send you any that are newer and certified.
  15. SP1 has never been removed from the website or Microsoft's servers. It was just....hidden from public view. As for all download of teh JVM, they're not supposed to include it in any future releases. However with that new Sun deal, they can however fix any issues with it, but can't update it.
  16. no..... /c: passes the arguments to setup_wm.exe. no need to extract. If that doesn't work (I've never actually used it, I use the OPK version of WMP9 on its own without the MM2. You could create a iexpress package with those arguments, and then you would just use /Q:A /R:N for switches. greenmachine.msfnhosting.com On the left, should be exampes of IEXPRESS usage.
  17. maybe because some people want it removed, and then they installed the full version plus update, and it saves alittle room? Wouldn't know how it would save space from SP1a as it's not even included, but SP1 is understandable. Also, you can still download SP1 from the Microsoft website.
  18. LOL. But, sorry about my ignorance, when will the program be released as stable (non-beta)? I don't want to go through 35+ pages... and now for a sarcastic reply...... when a good majority of the bugs are taken care of? when he wants to? when people stop posting bug reports? when the madness stops? when life isn't too hectic? when's good for you?
  19. did you put the WINNT.SIF in I386 on your CD?
  20. CDIMAGE just creates dynamic links if the files are identical. Not compressing. It just writes the file ONCE instead of however many times you have it.
  21. is yoru test Machine not XP? Maybe you have Home Edition?
  22. I believe I was the on that thought he was being legit. Bad Gamehead.....always on the look out for those pirates. Perhaps MS has a KB article on it? Never know.
  23. Anyone interested in testing this version? I think I fixed most of the bugs in the last one, while retaining the same functionality. MOVED TO FIRST POST
  24. try adding updates one at a time? remove the ones taht pertain to Media PLayer? The real question is, why are yo installing WMP9 after running it's update? Wouldn't you want it to be installed before updating it?
  25. @AztecMystic It's most likely that you're using the VMWare to test. It doesn't detect a single bit of hardware the a normal machien would except maybe the prcoessor. It most likely works on a normal workstation.
×
×
  • Create New...