Jump to content

Alanoll

Patron
  • Posts

    5,494
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Alanoll

  1. added Code tags, and removed your serial number from your file. Does the CD boot fine without the Winnt.sif file on it? Were you installin it the first time on a clean system? Make sure CDROM is set in the boot options as before your Harddrive in your bios.
  2. / should only be used to seperate folder and file. either remove the / and put pro1.dat in the BOOT folder, or make the / a \ and put the pro1.dat in the root of your structure (wher win51 and what not are)
  3. topic moved to proper forum
  4. 4 posts? please don't do that I believe it originated at neo win .net
  5. correct me if I'm wrong (and please do), but this is a program to make customized images on an already working machine right? then burn them, to get to others.... sounds good for certain situations, like you said multiple family members....or even multiple network environments..... but wouldn't it be cool, if someone create a script so that the Install was created dynamically like this is, but from CD. That would be sweet. Not bashing your program, very in genius. Probally mark it up with WPI, another great program. I'm sure sooner or later, I'll find a use for it I found one for your last one.lol. though not for a Windows XP cd. lol.
  6. oooooh, wow. I think I only have 29 programs install on mine..... I have a seperate disk to do the rest for me. (And to think, I use DVD's) lol
  7. cdshell.ini should reside in the BOOT folder on the CD. you may just as a test, mount the image as a virtual drive and then have VirtualPC grab it for the CDrom.
  8. when trying to "install" Windows, are you trying to use the menu from within indows via running CDShell.exe? if you have chain \winxp.dat then winxp.dat should be at the root of your drive. If you just have chain winxp.dat then it needs to be in the CDShell folder.
  9. use a file called OOBEINFO.INI there should be sufficient documentation in the deployment documents on the Microsoft website.
  10. Apple Quicktime I believe is the culprit. as for writing it in DOS, open up a command prompt, type EDIT, and then in the editor that opens, open your cleanup.cmd and type in the charracter there.
  11. i would personally recommend using XPCreate for hotfixes..... I haven't seen a batch file (jdoebeck's) that screws anything besides the SR1 on WU.
  12. loader.bin is from CDSHell.
  13. good thing you searched before posting eh? depending on how you were installing the drivers, you could very well be in the wrong forum. the switch for the InstallShield side, would be to use the -r and record a ISS file. http://unattended.msfn.org/xp/applications/installshield.htm
  14. @ralexand88 the easiest thing for you to do....would be instead of have ALL the hotfixes under ONE key, like 1, 2, 3, 4 but instead create another key for the next hotfix. so instead of... REG ADD %KEY%\001 /VE /D "Preparing Installation..." /fREG ADD %KEY%\001 /V 1 /D "%systemdrive%\install\prepare.cmd" /fREG ADD %KEY%\001 /V 2 /D "%systemdrive%\install\prepare.cmd" /fREG ADD %KEY%\001 /V 3 /D "%systemdrive%\install\prepare.cmd" /fREG ADD %KEY%\001 /V 4 /D "%systemdrive%\install\prepare.cmd" /fit would be REG ADD %KEY%\001 /VE /D "Preparing Installation1..." /fREG ADD %KEY%\001 /V 1 /D "%systemdrive%\install\prepare.cmd" /f REG ADD %KEY%\001 /VE /D "Preparing Installation2..." /fREG ADD %KEY%\001 /V 1 /D "%systemdrive%\install\prepare.cmd" /f REG ADREG ADD %KEY%\001 /VE /D "Preparing Installation3..." /fREG ADD %KEY%\001 /V 1 /D "%systemdrive%\install\prepare.cmd" /f REG ADD %KEY%\001 /VE /D "Preparing Installation4..." /fREG ADD %KEY%\001 /V 1 /D "%systemdrive%\install\prepare.cmd" /f
  15. i should point, i missed it the first time.... "md c:\fred"".\regedt32.exe /s .\AutoLogon.reg"cmdlines.txt runsin the directory it resides. So if you're on a CD, like a normal disk it would be like D:\$oem$ regedit won't work unless you have regedit32 in $oem$. Try removing the .\ on both regedit32 and autologon.reg. Though regedit32 is in the PATH variable (in the systemroot) you specificed a path with .\ and [Command] should be [Commands]
  16. eh, most don't know how to use it to begin (the code tags).
  17. well, I hear a few people have wanted mine...... i themed it to LOTR. hehe. I shall have to consider letting people have it.
  18. there are already ones created by Windows install. just open up a search window and ahve it search for *.log that will bring up the logs. The ones you're lookin for are in Windows or in a subfolder in Windows.
  19. only place I know of. And most of the links are probally bad.... http://www.msfn.org/board/index.php?showtopic=8041&st=240
  20. ah. Sorry. i've never actually used it. But then again, i don't use DOS on the CD except for installing Win98 and then i keep 8.3 naming for the Win98 files and what not. I personally use PaquetBuilder to make SFX's. Gotta buy it, but it's really nice. www.gdgsoft.com never tried FreebyteZip. hmmm, if you're really good with DOS commands, for the script you could use FOR commands along with the DIR command to output the list to rename.txt
  21. added Windows Post-install Wizard 1.2 Beta to the list under request.
  22. the kernel problem [bM]Crusher is because that VMWare doesn't emulate the multiprocessor. There are two kernels, ntkrnlmp.exe is the multiprocessor, and ntoskrnl.exe is the single processor. the mp one is renames to ntoskrnl.exe during setup. FOR /F "tokens=3 delims= " %%A IN ('REG QUERY "HKLM\SYSTEM\ControlSet001\Control\Session Manager\Environment" /v NUMBER_OF_PROCESSORS') DO SET NUMBER_OF_PROCESSORS=%%A bootcfg /copy /D "Windows XP Professional" /ID 1if %NUMBER_OF_PROCESSORS%==2 goto DUALREM ----For Single procbootcfg /RAW "/Kernel=OEMKrnl.exe" /A /ID 2goto End:DUALREM ----For Multiprocess/Hyperthread procbootcfg /RAW "/Kernel=dualKrnl.exe" /A /ID 2:Endbootcfg /Timeout 2bootcfg /Default /ID 2I modified the code of the original to suit for multi/single prcoessor. the for line is neccesary and this has to be in it's own batch file. It also creates a copy of hte original line incase it doesn't work, you'll still have the original to finish testing with, so you know what works and what doesn't to narrow your tests.
  23. i'm not even sure that RIS processes cmdlines.txt but... instead of calling those commands, have it call like pause.cmd create a pause.cmd in the same directory as cmdlines.txt and inside have ECHO YAY!! IT WORKS!!PAUSEPAUSE(two pauses jsut in case you press a key without meaning to) also, for use of reading, please enclose your code in [\CODE] tages (minues the \)
  24. or me!! I know a wee bit about it...lol did anyone figure out what happened with the cmdlines.txt thing? if it's a RAID driver, it could have become corrupted. But the user issue is another question. Did either of you modify any of the core system files? like any in I386 besides svcpack.inf ?
  25. yeah.... HKCU seems to work better then HKLM. Also more logical.
×
×
  • Create New...