TranceEnergy

I dont understand your reason for using rvmi.

I can't wait till ReactOS gets proper audio support. It's going to blow xp 32bit out of the water. Now if only they would ever 64bit it. =)

Nlite also doesnt remove all keyboard layouts. But i know nuhi knows this, have told him long time ago.

That's really neat, but if you could post in some detail to what you did exactly, it would be easy to replicate the steps deemed necessary. Not all run xp xpsp3.

There is one thing i would like to see in future nlite, and that is simply possibility to review the changes nlite will make to the windows source folder, and editing them. Then one could really easily create a very tight source. In short i would like to have more control. More ON topic however; i simply removed dosnet.inf as well as removed all files for doing upgrade installs. Now nlite bitches about missing dosnet.inf etc. Well install in vmware went perfect without it, not modified by nlite, clean image otherwise. What gives? Trying to run the install in vmware, after using just options bar in nlite (settings windir, and usb patch etc) on install xp asks for sp2.cat as well. Setup does continue after clicking cancel for the file on 2 popup boxes. Now since the install ran just fine before i nlite modded it, i guess its nlite or what?

That would involve backup the system or creating another partition. Ergo, it's not a solution. Sure it will do the job, but it isn't very helpful, anyone could think of that or do that. Better to have a solution that doesnt require to install a os to make an install for os. As you can see that is ridiculous.

nlite will copy all the files in that folder, it doesnt matter what inf file you select.

Agree, too many in the kitchen=)

If your key is invalid, its invalid.

Support for 64bit? XP x64 and 2003 x64 specifically?

I don't see a reason why not. I'm trying to follow the guide for xp x64, and while partially successfull, it wont boot =). But thats because i need a multi boot - boot image. I see no problems in following that guide for 32bit systems. AFAIK the only thing you lose by following gosh's guide is ability to do upgrade installations.

I have reported this years ago, there are several languages nlite will not remove from xp x64 sp2. or sp1 for that matter.

I'm following this for xp x64 with sp2 slippy, and it's quite evil, hehe (and no, picture isnt faked). Thank you so much, im so reading/loving your unattended stuff. Kick a**! Snapshot after having copying $WIN_NT$.~LS and renaming it to Install, as guide says, before any other changes. Note: Saved 122MB with this process on amd64&i386 folders. SP2 US. update: I find it more or less impossible to know for sure what i386 or maybe its amd64 entries to replace with BOOT etc. in the setupldr.bin file. there are 7 entries with i386, and 8 or 9 with amd64. edit: i found out what to replace according to a 32bit version of same file, but process still leaves me with booting problems, incorrect NTLDR. update2: I think i have figured it out now, lol, Need 2 files to be able to install: WIN51AP and win51ap.SP2. There's also Win51 file, but windows will install happily without it. At least thats what my short tests tell me in vmware.

As long as you: * Copy iso file you made, to a location you deem safe. Perhaps make a folder calling DVD-version f.ex and put file in there. * Save presets for your different configurations you'r okay. (Copy last_session.ini and rename it, and disable/enable copy preset to iso to your liking) * Point nlite to a NEW empty directory when you want to start make another install, your safe. etc. I would try using an usb stick instead if you only have cd-drive on some pc. There are many guides on this, google it.

Hello folks. I need a small neat utility that will enable me to create a batch file for creating an xp cd image. Thus i need a program such as topic says: Need a utility that can insert text from file to any file, anywhere. I am looking right now to specifically input 2 lines of text into the end of file, or at starting from line 15 f.example. Preferrably able to be run from anywhere.

I will perhaps do that, tho i dont mind doing some more googling atm. Running first install in vmware now, i have selected to not install more or less everything i could through winnt.sif (using link as reference), keeping paint etc. I kinda wish i did this way back. This is so much fun =) edit: well it's working great so far. I really like the higher level of control on whats going into the windows install. I used gosh's guide to create smaller xp source(only upgrade install option lost), which with a few modifications works on x64 as well, saved about 130mb on iso =)

I see most hotfixes contain CAT (security catalog files) named in the 8character already. Can i just call them, or do i have to extract them? If i write KB111111.cat (example name) under productcatalogsdata, will it then understand that that comes from kb111111.exe file? I somehow think so. This is very interesting process =) I am very interested in getting rid of the .cab archives, using them in extracted formated if possible. Reason why is to be able to update contents, and modify, without having to de-cab and re-cab everytime. I guess you dont know that one?

there are a couple of possible culprits, last preset?

well i use xp 64bit version , while you use 32 bit version. So i use this f.example. : regedit.exe /s %source%tweaks\Remove_Startup-Java.reg so is your regdt32-.exe properly named?

That's what compability selection is for atm. But i welcome more work on nlite. I'm wondering if nuhi has a copy of x64 xp, and if he does if it would help nlite on xp x64 development. There are so many little things, and some big ones, not really working atm. Tbs, im considering buying xp x64 for nuhi himself =)

To what end? What purpose? What is the point of doing 1 install to just reinstall after that again? I can think of some reasons but i want to hear yours.

Kurt, i see you have had some experience with svcpack method with 64bit xp yes? In any case this old bird is tired of reinstalling and reupdating iso's. And with what i have now delved into, its more or less the only way suitable for me. Meaning a install of hotfixes at install time would be better, and eventual batch scripts to update/remove outdated files. I looked up microsoft's website and unattended here at msfn, and now looking through some links, but not had any concrete examples as of yet. Any input = most welcome as always. edit: I found this on my iso (svcpack.in_) under amd64 folder. Which i found a bit weird, since it says i386 in that file... [Version] Signature="$Windows NT$" [setupData] CatalogSubDir="i386\hotfixes" [ProductCatalogsToInstall] [setupHotfixesToRun] One thing curious about is the Buildnumber, seeing as i will update many things including kernel. Does it matter much if that number is different much? I assume it has some kind of purpose.

i just remember i have linked to this before... on this forum.. I figured out how to slipstream SP2 for an x64 XP CD fileset while from 32bit Windows. Download the Windows2003 SP2 32bit version (WindowsServer2003-KB914961-SP2-x86-ENU) and the x64 SP2 (WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU) files from MS. Extract them both with your favorite compatible file archive util ( I used Uniextractor ). Copy the binary files (dll/exe/msi) from the 32bit version's 'update' folder into the 'update' folder on the 64bit version. I used nlite 1.3.5 to do the integration but I suspect the appropriate commandline execution of 'update.exe' would also work. http://neosmart.net/blog/2007/windows-xp-x...ack-2-released/

The steps wasnt that bad, but i dont remember the details. But i know it is possible. I'd try google. I'm too busy trying to figure out something myself, to google it for you. Sorry.

It is, but not by normal methods.