galvanocentric

Accessability you can turn off easily. Just search ref.chm. Should be under [components] if I remember correctly. OE you might be able to turn off ACCESS to, but Microsoft doesn't want to admit you can go uninstalling bits like OE, or MSIE, or Windows Media Player, and still have a working OS, because that'd put them on very shaky legal ground right about now. They'd also lose the monopoly they have. Just use nLite.

Am I the last sane man? VMWARE!!! Then pick up a 250 pack of blank CDs and a 50 pack of blank DVDs.

Make a command script, call it useraccounts.cmd or whatever you want. Just make sure the extension is cmd. Then paste the following: @echo off net user MrFoo Bar /add /fullname:"Mr. Foo Bar" net user MrsFoo Bar /add /fullname:"Mrs. Foo Bar" net localgroup Administrators MrFoo /add net localgroup Administrators MrsFoo /add exit MrFoo and MrsFoo are the usernames. Bar is the password for both. You can ditch /fullname:"whatever" if you don't want it, I like having the extra details. Obviously, for net localgroup replace MrFoo and MrsFoo with whatever you chose for the two usernames.

My thoughts exactly. Numlock shouldn't even by rights exist anymore. I've seen it on laptops, for Christ's sake. They don't even have a separate pad for entering numbers! Jesus...

Please, use VMWare and burn your OS installation to an ISO. You'll save a LOT of frustration.

I've had a theory I've always wanted to try out. Compress all your OEM files into a CABinet and obfuscate the title as say, s049a_x9.cab. Store it in i386. Build your own bootloader (very easy, programs will make one for you) that loads i386\winnt.cmd. Modify winnt.cmd so it reads as follows: (CD-Drive detection from Firefox guide) @echo off FOR %%d IN (c: d: e: f: g: h: i: j: k: l: m: n: o: p: q: r: s: t: u: v: w: x: y: z:) DO IF EXIST %%d\CD.TXT SET CDROM=%%d expand %CDROM%\i386\s049a_x9.cab %SYSTEMDRIVE%\OEM_FILES %CDROM%:\i386\winnt32 /s:%CDROM%\i386 /unattend:winnt.sif /copysource:lang My theory is, that would expand the OEM files from an obfuscated CABinet to C:\OEM_FILES. You then under [unattended] in winnt.sif set OEMFilesPath to C:\OEM_FILES and go from there. Only problem would be that drives wouldn't be configured yet. I think however that if you threw FDISK into i386 and called it, creating say a primary partition 15% of the total size of your disk, calling it C:\, that might fit the bill...

A better method would be to install VMWare and test ISOs thereabouts... But yah, you can easily find out whether things are named correctly. Go to the command prompt (run -> cmd) and type in dir C:\XPCD\i386\winnt.* (or wherever you've stored your happy little XP CD (you know, before turning it into an ISO or into a CD) You should see winnt.sif. If you don't, you've found your problem.

The command script is for something else entirely, don't use. Everything looks kosher to me... You filled out everything that the Support Tools program told you to?

I like this method because it cuts a step from the total installation time. Begin by downloading Sygate 5.6 from Downloads.com (don't do it through the Sygate website, TRUST ME ) Run Sygate as if to install, and when it's finished with extraction, go to your %temp% directory. You should see an arbitrarily named MSI file. Run it if you want to make sure it's the Sygate MSI file, then copy it to another directory. Close the installer and the MSI file in %temp% vanishes mysteriously so you don't get to do what you're about to do. This is the same procedure you can apply to pretty much 90% of modern InstallShield packages, really. MSI is (thank God) finally becoming an industry standard. So, anyway. Rename the MSI file to sygate.msi and when setting up RunOnceEx.cmd use the following syntax for installing Sygate: sygate.msi /qn REBOOT=ReallySuppress Should work with no problemos. I also use this method to install Daemon Tools and it runs fine, no hardware wizard problems that other people complain about.

Windows can't run thirty programs at once, even at ten installations it begins to lag noticabily. This "should" prevent it, and does to a degree. Only with crappy installer systems like Wise do things get fouled up.

You can put environmental variables in your *.reg files but be prepared for the unexpected. You are then leaving variable inperpolation to each program, instead of to Windows. Imagine if Ad-Aware, for example, though it lived in the root of a drive called %ProgramFiles% instead of in C:\Program Files\Ad-Aware, get my drift? If you use the $Docs and $Progs folder structure you should be able to with perfect accuracy throw those shortcuts to the correct location.

Ah, I thought this was in discussion of the paid version, not the trial. Owning Nod32 does come with certain perks.

I buy all my music from the little stores that sell trades. Trades, for those not in the know, are when small CD stores pay to get your old CDs, or trade 'em. Then they can keep a fresh inventory. So... I don't pay a dime back to the RIAA. I do pay for concerts, etc... so I feel like I'm one of the only ones who is soley supporting the artists, not the RIAA.

Easy enough to get from the Nod32 website, no?

I assume you've replaced the serial number (Xed) with your own? And if not, that's your issue. And don't ask me for a serial number.

Might I recommend a simpler, more "kosher" method? By virtue of the administration edition, I have put together a config.xml file to play with. Simply run setup.exe as follows: setup.exe /silentmode /cfg=config.xml /settings=settings.xml /instmfc I found this to be a helpful URL: http://216.239.39.104/search?q=cache:WJOv3...lient=firefox-a Very helpful indeed, really. Everything "should" work, in theory... Worked on mine in any event. config.xml

Although I'll get a lot of boos, Microsoft has certainly, as their motto goes, set the standard for silent installations. If they'd only come up with msiexec and the MSI schema a few years prior, we might not have a need for this forum. Thanks!

I actually went and took this a bit further. I did the SFX compression of the AIM folder, but I used these settings: ;The comment below contains SFX script commands Path=AIM SavePath Setup=REGEDIT /S %systemdrive%\install\AIM.reg Silent=1 Shortcut=P, "AIM.exe", "AIM", "AOL Instant Messenger Chat Client", "AIM" That both saves space AND eliminates the need for the clumsy XCOPY and MKDIR commands.

Thanks, this really helps.

Wow, as Nero keeps overcomplicatings things, y'all keep undercomplicating them. And for that, I thank you.

Very simple, actually, and if you follow the PDF, it isn't too difficult to understand. Install Nod32 administrator edition. Make a config.xml file. Then use the switches from the happy little PDF to load config.xml, sort of like setup.iss but more powerful.

For Python: http://diveintopython.org/ http://www.vex.net/parnassus/ http://www.pygame.org/ http://docs.python.org/tut/tut.html

Yes, I've tried it. At least on my copy of WXP SP1 / SP2, you can go into the options CPL and turn off the keyboard shortcuts.

When it does that, go to options and turn it off.

Havnt played with nlite yet, but i used a regular 2003 Server Standard as the source. If you use Virtual PC to test the ISO's just create a new one and try it out. Hehe. I'm a ballsy lil guy. I use my laptop.