tewk_dawg

Update - Tried both methods - neither worked for me. I'm building the unattend XP on an IBM T60 Model 2007CTO it has a Intel Duo Centrino chipset with an Intel integrated NIC. I'm starting over from XP SP1 today, the machines also have SATA drives, which isn't a problem since I have it booting from the DVD and installing everything works great. The clean build does not install the Multi Processor. I'm beginning to doubt myself and rebuilding our XP disk from scratch, maybe I lost a file or 2 along the way.

I do much the same except my machine(s) do not hang, they work for the most part but lock up when I disconnect the power supply from the laptop, the only other thing I noticed was that they do not show the duo core processors in the task manager, and oddly enough the control panel will not change from the default XP display to the classic display. I've tried to use the uni processor build and have much the same problem, everything was OK for a while (first 2 days) until users starting complaining about the power issue with laptops. Either way I'm trying your methiod today and will also let you know. Regards

For what's it's worth, I wanted to use some vbs scripts for my application installs using the runonce. cmd method. We have our applications (MSIs) using transform files that we code through a vbs file. Could not get it to work, my guess is that the windows script handler is not available, although we haven't tried copying this to say... the system32 folder and executing from there. Experience tells me that the vbs currently fails using this method at the T-12 mark, so we went back to batch files instead (for the time being). If anyone has had any luck, I would be interested as well.

Joja15, You have another option available that would be better than all these in my opinion and it's what we use when we install the Tablet Edition XP on to Tablets. What about a USB external floppy drive using a network boot disk from either http://www.netbootdisk.com or http://www.nu2.nu/bootdisk/network/ either of these can auto detect the NIC and load the right drivers to boot to a network share. BTW - I found netbootdisk to work the best. Good Luck - Hope this helps

Thanks for your help so far. I'm still not having much luck with the unattended install from the network to a tablet PC. I get a not enough memory error when I start installing Windows XP Tablet Edition. "setup is out of memory and cannot continue" I have googled this and not found much. I'm able to map a network drive and start the installation by the command line, but the first file it looks at is the dosnet.inf which has a line specifying the minimum amount of memory. I have tried adjusting this all the way to zero but still receive the same message. What I have noticed is that the amount of available memory when booting from a win98 boot disk seems to be much less that what is expected when booting from the tablet. I'm going from memory myself here and I think it said 11kb & 22kb when the screen flashed by. When I ran the same boot disk on a desktop it showed 78kb & 35kb. I don't know if this is the culprit but seems to be a good place to start. Any help at this point would be much appreciated - as I am stuck for today. TIA

Hi all, I have been using the unattended install method on desktops and notebooks succesfully for some time now, but I've just been handed a tablet along with the 2? CDs to do the same thing. I have searched for methods on slipstreaming within this forum, and the differences that may exist in the unattended install. Has anyone done this and had successes or failures, can they share their experiences? Is it much different than running the desktop/laptop unattended install. Thanks

Thanks for your input, changing the scripts is not in our control and therefore we're unable to do this, although I'm not sure if this is possible but would be interested (even if we can't change it) anyways. The scripts are ran through the logon to the domain each time a user logs on through a policy. Keep the suggestions coming. Thanks again!

Prevent XP machines from joining the WINNT 4 domain. Hi Folks, I was wondering if this exists in XP under the local security policies and if anyone has tweaked this with a registry tweak. What I'd like to do is prevent an XP machine from being joined to any DOMAIN in WINNT, I would also like to do this in the unattended install. While ervything was going well with the unattended install CD. This has become problematic. We have some NT4 domains that when the machine joins a domain a script is run and changes the common start menu location in the registry of the local machine to point to shortcuts that are common to all machines. When this script runs on XP it prevents the start menu from being displayed or it takes a very long time for the menu to appear. Ideas, suggestions? Thanks

Works great! No problems to report.

Trying it now using the INI method, will let you know in about an 20 minutes. Here's my command line in the runonce file and the ini is below. REG ADD %KEY%\005 /V 2 /D "%systemdrive%\install\WINAMP\winamp505.msi /qb INI="%systemdrive%\install\WINAMP\winamp.ini"" /f [sETUP] XLIBRARY=1 XJUMP=1 XMODERNSKIN=1 XAUDIO=1 XNAME="xxxxxxxx xxxxxx" XKEY="xxxxx-xxxxx-xxxxx-xxxxx" XQUICKLAUNCH=1 INSTALLDIR=C:\Program files\Winamp XSKINSETTING=Winamp Modern

Forget it..... "%systemdrive%\install\WINAMP\winamp504.msi /qb INI="%systemdrive%\install\WINAMP\winamp.ini"" /f Works just great!

Folks - I have been trying the winamp MSI for the last few days and haven't got a clean install from runonce yet. Here is my runonce command line syntax, I know it's gotta be the syntax, I just can't get it right. Some much needed help is required, when I run the command line in a command prompt it works fine. Below are some other commands I have tried without much luck, can someone shine some light? By the way the install works great with the INI file except when I contradicted myself in the INI by telling it that I want Classic Skin and Modern Switch turned on XMODERNSKIN=1 - took me a while to figure this one out. XSKINSETTING=Winamp Classic XMODERNSKIN=1 Now looks like this. XSKINSETTING=Winamp Modern XMODERNSKIN=1 %systemdrive%\install\WINAMP\winamp504.msi /qb INI="%systemdrive%\install\WINAMP\winamp.ini" /f <----doesn't work, same line works fine when ran from the command prompt. I relaize that I'm missing the quotes at the beginning and end of the line. But when I do add them it also doesn't work. "%systemdrive%\install\WINAMP\winamp504.msi /qb INI=%systemdrive%\install\WINAMP\winamp.ini" <----doesn't work "%systemdrive%\install\WINAMP\winamp504.msi /qb INI=%systemdrive%\install\WINAMP\winamp.ini" <----doesn't work C:\Winamp504.msi /qb INI=C:\winamp.ini <-----works fine when I run it from command prompt and move the files there "%systemdrive%\Winamp504.msi /qb INI=%systemdrive%\winamp.ini" <-----also works fine when I run it from command prompt and move the files there

Why does this not work in a batch file, yet works line by line in DOS window. I get "f was unexpected at this time." I simply want to rename my cdrom to Z when all is said and done. --start of batch file--- for /f "Tokens=3" %f in ('"echo list volume|diskpart|find /i "rom""') do set cdrom=%f mountvol %cdrom%: /L >%temp%\guid.txt mountvol %cdrom%: /D for /f %i in (%temp%\guid.txt) do mountvol Z: %i del /q %temp%\guid.txt --end of batch file--- On a different subject: Does anyone know how I can put a timer on my version of Windows XP to expire after a certain amount of days. I've thought about a scheduled task that simply renames the password for the local admin account, but it seems to simple and easily detected, I was wondering if this has been discussed before anywhere?

I have been trying to extract the driver files for various hardware components, I have been creating my drivers directory using the OEM Drivers path in the winnt.sif file such as Drivers\000_chipset; etc. What I don't know enough about is the setup file with the drivers called Setup.DIY for example here's the contents of a Setup.DIY {\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset134 MS Sans Serif;}} \viewkind4\uc1\pard\f0\fs16 pci\\ven_8086&dev_1019&subsys_02a71014 \par oem9.inf \par \par } I'd like to know if this file is required (if not great - I'll just remove the file), can you combine multiple Setup files by simply appending the file with another file, or in other words can I add this to the above to make a single file. The problem I'm having is when I copy the files for one NIC to my 001_network folder and then try to copy a second set of NIC drivers (which also includes a Setup.DIY file) It, of course, prompts me to either overwrite the file or not. This not only happens with NICs, but also Video, SMBus & Sound Drivers. {\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset134 MS Sans Serif;}} \viewkind4\uc1\pard\f0\fs16 pci\\ven_8086&dev_1013&subsys_02851014 \par oem6.inf \par \par } If anyone else has come across this I would like to know what they did to resolve it, maybe it has something to do with the software I'm using called WinDriver. I wanted to ask before I started experimenting and creating a bunch of coasters. This cannot be tested with Virtual PC, since it doesn't look at the specific drivers for these very specific hardware devices.

Wanted to say hello to all in the forums and introduce myself, have been poking around for a while. Just wanted to start posting or helping out where I can.