gamehead200

I've finally figured it out... I chose an option in nLite that removes the net.exe file... Just... I don't know which component removes it and I'd rather not use the box to keep files... Anyone know what option removes net.exe? (I know, this should be in the nLite forum, but it started off with cmdlines.txt not working) Edit: I was removing Command-Line Tools without thinking... Hopefully it will work this time!

Remember, now... I used nLite as well as gosh's method... Also, the winnt.sif file is working fine in the BOOT folder... The BOOT folder has all the files necessary to partition the drive, etc. Also includes the setup file, txtsetup.sif... The I386 folder has all the necessary XP files to be installed. The rest of the files in the root of the CD are for my CD's menu, such as DELOAD.BIN, DISKEM1X.BIN, LOADER.BIN, and DISKEMU.CMD... The DAT files are Disk images... If you don't know how gosh's method works, I suggest you read his tutorial: http://gosh.msfnhosting.com See screeny:

OK, so I've slimmed down my install to about 150MB using nLite and gosh's method (yes, both of them). My unattended install works fine, except for the fact that cmdlines.txt is not getting parsed. I have my $OEM$ folder on the root of the CD. Here are the contents of my winnt.sif file: [Data] Autopartition = 0 MsDosInitiated = 0 UnattendedInstall = Yes [Unattended] UnattendMode = FullUnattended UnattendSwitch = No OemPreinstall = Yes OemSkipEula = Yes FileSystem = * WaitForReboot = No NoWaitAfterTextMode = 1 NoWaitAfterGUIMode = 1 TargetPath = Windows DriverSigningPolicy = Ignore NonDriverSigningPolicy = Ignore [Display] Xresolution = 1024 Yresolution = 768 BitsPerPel = 32 Vrefresh = 60 [GuiUnattended] EncryptedAdminPassword = No AdminPassword = "123456" TimeZone = 035 OEMSkipRegional = 1 OemSkipWelcome = 1 [Components] Indexsrv_system = Off [UserData] ProductKey = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" ComputerName = SLIM-XP FullName = "Your Mom" OrgName = "Home" [RegionalSettings] Language = 0409 [Networking] InstallDefaultComponents = Yes [Identification] JoinWorkgroup = HOME Everything looks fine to me. OemPreinstall is set to YES, so everything in the $OEM$ folder, in theory, should do something, right? Here is my cmdlines.txt: [COMMANDS] "useraccounts.cmd" "REGEDIT32.EXE /S tweaks.reg" And my useraccounts.cmd: net user Michael nottellingyou /add net localgroup Administrators Michael /add net accounts /maxpwage:unlimited EXIT All I'm trying to do is basic stuff. Adding a user account and adding some registry tweaks. None of this happens during the install. I've tried different things for the past few days, reinstalling XP on VMware about 20 times, but NOTHING works. One more thing; All the files (cmdlines.txt, useraccounts.cmd, tweaks.reg) are in the $OEM$ folder. What am I doing wrong!?

Is there a list of files somewhere that no other program uses but Winlogon? Aegis, you might know this one...

Participation and a intimate relationship with Windows. <{POST_SNAPBACK}> And once you're in, you get a free T-Shirt!

Who wasn't? As soon as I heard Count Two: Not Guilty, I was like, "That's it, he's not going to jail!"...

CNN said 18+ years...

Watching it now...

ROFL!

Aegis, check your PM as well!

Good thing my school switched to optical mice... Now, now more of the mouse balls are missing!

Why is this in the Windows XP section? [ Topic moved. ]

I knew this was going to be a joke like this!

LMFAO!!! That's a keeper!

Downloading it ATM...

That is exactly what I was referring to!

Listen, the ONLY thing that Apple will be changing in their computers is the motherboard and processor. Everything will remain the same. According to this article, Macs will be able to run Windows as a dual-boot system, but PCs not using the new Mac processors and motherboards will NOT be able to run Mac OS. Mac OS is hardware dependent. Windows is not because there are many drivers for every single piece of hardware out there. As I said earlier, it MIGHT be possible to run Mac OS on our current (or future) PCs with a few hacks here and there. The transition from PPC processors to Intel processors will also reduce a lot of headaches for developers. They will not have to write a program differently for Macs because they will no longer be using PPC processors. As I was chatting with Cyberpawz last night, he was telling me that the latest version of Mac OS X (Tiger) will not have to be changed since it is already ready for the use of Intel processors. If all I've said here is correct, then it seems right that my Mac OS X (Tiger) DVD did not boot on my Intel powered laptop. One system to rule them all.

Don't bother... Its too slow to use!

Mac OS X will NOT be compatible with PC hardware, but Windows will be compatible with the hardware the Apples will use. However, there are talks going on about hacks that might be available to let Mac OS X run on PC hardware.

LMFAO!!

You prefer binary!

G4TechTV wanted to give the show a new name. "The Screen Savers" is now known as "Attack of the Show", which features a lot more gaming stuff. This is old news. Kevin Rose left G4TechTV about 2 weeks ago... His first episode of Systm has been online for that same amount of time. http://www.systm.org/

Nice app list! Thanks a lot! I just added a bunch of these to my iPod shuffle! BTW: i pwn j00. 64m3h34d200 > j00.

So how long is it until this installer is ready?

Don't post this as your first post. This is considered spam if its your first post. Please read the rules! [ Topic closed. ]