Alanoll

REG ADD %KEY%\066 /VE /D "WinZip 9.0" /f REG ADD %KEY%\066 /V 1 /D "\"%Programfiles%\winzip\winzip32.exe\" /noqp /autoinstall" /f That should work.

well, I've redone the site twice already. Everytime it's been "different" and I didn't feel the need to upload it right away. I'm waiting for to be completely finished before completely releasing it As for teh Nov22 thing, well...I originally gave it time so people could suggest things to be added. Now I'm just waiting for the final pieces before I continue work on it. About 2-3 weeks after the initial renovation of the site, it will be updated again.

Correct, Workstation service is running yet. I also believe you can't force it to start either ( NET command)

sure.... I'm working on the custamization branch, and then I have the reference section to go (most is the same from the old one.) Then I'm just waiting for the PHP stuff to be completed, and I'l integrate it into the site.

you removed WINNTBBU.DLL from TXTSETUP.SIF. Go back to your original disc, and add the entries back and copy the file back.

seperation of the different trees for maintenance? If you look at then, one does the HKCR, one does HKCU, one does HKU, and one does HKLM. That's my best guess. They're all loaded at the end of textmode setup.

you forgot Windows Installation Helper Utility. There is a subforum for it.. This is what I use currently. (Conditional Statements)

ABSOLUTELY NO NEED FOR YOUR SECOND TOPIC! Do it again, and you will be warning.

next time, just use the little PM button at the bottom of my post... 1. About previewing. Actually despite command belief, you don't need a VM to preview. Open winnt32.exe in Windows. It should show you're new setup screen. Just cancel setup and you're fine. 2. What do you mean? 3. Depending on the VM software you use, there is a Screen Capture function. Typically in one of the menus at the top of the window.

how is it wrong? 4.3 is less then 4.12! 4.3 however is LARGER then 4.1.2

.BIN is actually an assembly file, not a compiled upper level language. You'll have to decompile it to find the exact HEX address to edit.

Gosh just starts Windows setup. It's fully compatible with SP2. jdoebeck's batches however are not.

edit setupldr.bin Enjoy! P.S. That's the majority of txtmode setup right there. But I don't know where to edit. I'd have to disassemble it. Which I won't do for now.

NOT nlite related.

can't do that. the update pack uses SYSOC and Windows Setup to install. SP2's standalone CD has neither.

but you still have to do the brute force of finding the switches and such I could have sworn I saw something similar to this before....oh well...

here's what you could do.... use BartPE. That will load up Windows from the CDROM. Execute the frontend, but have it just write the neccesary file (a predetermined file name that will be already specified in your setup files) and then execute setup like normal. Bare in mind I have not done this, but logistically it should work. You may have to preformat however, but that can be done in a batch script or something.

REG isn't. Here you go reg.exe

and now to ruin everyone's parade tooting CMD line CDROM variables.... HE"S USING AN INF! Now that that is done... Here is what I suggest.... use %1% (it's either %1% or %1) This is the path to where the INF file was executed from. So example: HKLM,%RunOnceEx%\install01,"1",,"%1%\WIHU.EXE /SkipSettings /AUTOINSTALL=0 /INI=applications.ini /RestartWait=80 /log=%systemdrive%\wihu-apps.log" That will add an entry to the RunOnceEX with %1% being the path to WIHU. I executed the INF file with rundll32.exe setupapi,InstallHinfSection WIHUSETUP 128 ..\Unattend\RegEdits.inf So %1% becomes %CDROM%\Unattend\ It's more of a trick then anything else. Another thing would be to use the SourceDisks section in an INF file. I've never gotten it to work properly, but who knows, maybe you might. CHeck the Microsoft MSDN site for more details. There was also a post on here awhile back about it as well.

umm.... Good job! but not to be rude or anything, but you have to be like the 3 person to post this in a week Now I'm just gonna explain why I believe the IF EXIST checking for a file is better. 1. It can be expanded to multiple CDs. 2. If you are creating a MultiBoot CD, then the SourcePath then becomes something obscene And most people put their Unattend stuff in the root and not buried in folders. 3. EVERY XP CD has the Win51 file. 4. It only fails SOMETIMES with removable storage drives like ZIP drives. The SourcePath method locks you to a drive, a SINGLE drive. And like above, it gets alittle nasty when doing MultiBoot CDs.

I was quite impressed when my Hitachi failed....(i dropped it). I returned it under warranty, and the replacement was back in 1.5 weeks.

@]Bonkers[ Did you use nLite or remove WMP in anyway? It's something related to the WMP codecs and such. It's not a problem with the MSI. Sorry. Best guess... extract the file from your XP CD (it SHOULD be there unless you used a program to remove it) and put it in system32

i like Hitachi. Sure I run the risk of them failing, but they have a 3 year warranty compared to the 1 year most others have. If I keep things backup, I don't really care that it fails, I have a few spares in the closet ready to go with WIndows installed and everything just to put it in the system.

Are you refering to the CHKDSK taht runs if the system isn't properly shutdown or the like? If so, the problem is that there isn't a bit being set upon shutting down taht signals the system that it was shutdown properly. Nothing to do with ProfileDir