peachy

The Dell web site describes the 4600 as having 2 onboard SATA controllers. Thus you will need an appropriate 7-pin SATA cable to plug into the motherboard. Depending on whether your new hard drive has the old 4-pin Molex power connector (should work with your power supply) or the newer 15-pin SATA power connector (you would then need a 4-pin to 15-pin power adapter; unless your power supply has the 15-pin SATA power connector!) would be your other consideration.

monstersnatch, did you ever get it to work? I just finished creating a Windows 2000 unattended install CD and I just unpacked the latest G4xx drivers into my $oem$\$1\Drivers\004_graphics directory in a directory called G4xx, added it to my OEMPnPDriversPath and away it went, silently installing it for my G400MAX. No need for a setup.inf file.

Try ptedit.exe found on the second disk of your PM boot disks. It shows your partition table and you can edit if you see what needs correcting. But you should know what you are doing.

Dreamweaver MX 2004 is a good choice! It handles CSS better than anything out there and its WYSIWYG mode does faithfully render CSS properly 95% of the time. The nice thing about DWMX2004 is that if you use style sheets then the font rules in your style sheet are added to your menu for styling your text. That in itself makes developing pages less of a chore. The other neat feature of DWMX2004 is much appreciated by web application developers. It has built-in tools to add PHP, ColdFusion Markup Language, and ASP tags. It also has a library of basic scripts for using those scripting languages to interface with databases. I taught a web server technology course last fall and I showed the students how to quickly create queries and display output using DWMX2004 and a ColdFusion server.

Uhmm, need to click the mini-setup check box. Of course, it worked in Windows Server 2003 because it's checked by default and greyed-out!

Has anyone got sysprep to work in a volume licence XP so that it doesn't run the OOBE? In Windows Server 2003 if I run sysprep -reboot -reseal -quiet it behaves the same way as sysprep sysprep.inf -reboot in Windows 2000; i.e., completely unattended mini-setup. In XP it always prompts for the EULA, Product Key, Administrator password, computer name, etc, all things that have been specified in the sysprep.inf file. It's as if it's not even reading the sysprep.inf file. I have it in the %systemdrive%\sysprep folder.

Using the RIS setup wizard add the source for the install and feed it your unattend install CD/DVD/network share. It will create the appropriate directory structure for your RIS server.

I would suggest the best way to do this is to get the latest SiS graphics driver from Gigabyte and extract the files to your $oem$\Drivers\graphics directory and provide the OEMInstallPath in winnt.sif to the drivers. The resolution won't change unless the correct graphics drivers are installed and this is the method to use.

What is your motherboard and video card?

I don't have experience with Abit boards but mainly with ASUS and Intel. In the AMI BIOS of these boards with the Intel ICH4/5/5R, the SATA controllers are listed as IDE 3 and 4. If you have both PATA and SATA drivers connected, you need to go and change the Boot Drive Priority. By default the PATA drives are listed first. But if you highlight the first boot device and hit the enter key, you will see all the bootable drives listed. Then you just select the drive you want booted first, PATA or SATA, master or secondary. If the SATA controller is not native to the chipset, then it will be designated as a SCSI drive and you have to choose to boot from SCSI as the first device.

What you will want to do is have a logon script that calls a batch file that creates a local user account for the student if it doesn't exist on the computer already. The local account should be restricted to the Users group. You need to give the local user account the same password as the Novell client login so that the students won't be prompted for the Windows logon password. That's the way we do it here at work (a college). Read the Novell documentation on this. I believe they must have some. I don't work in our IT department, but I know enough about the general process we use.

Oops, didn't even realise I was in the wrong forum.

Well this is what I did and it works as WU reports no critical updates to download and KB839643 shows up in Add/Remove Programs. Installed DX9OPK in svcpack.inf and then call a batch file near the end of my RunOnceEx list that contains this: ECHO. ECHO Installing Security Update for DirectPlay Denial of Service Vulnerability (KB839643) start /wait %systemdrive%\install\hotfixes\DirectX90-KB839643-x86-ENU.EXE /Q /O /N /Z If it doesn't install, check the file KB839643-DirectX9.log in your %systemroot% directory because it will tell you why it didn't install.

ASUS, ASUS, ASUS! When I first got hooked on building my own computers rather than relying on someone else to do it, I didn't choose my motherboard. I had a friend who worked at a computer store and I asked him to send me the best 430HX chipset motherboard he had. He sent me an ASUS and I've never looked back. Currently on my 7th ASUS board in the past 8 years. It's an ASUS P4C800-E Deluxe. (I upgrade every two years or so and repurpose the older ones to friends or rope them into use as testing boxes!)

Don't do it in RunOnceEx. I've been grappling with this since last Thursday and have found the best place to do it is in the cmdlines.txt file directly in the $OEM$ directory. Just and the command like this: [COMMANDS] ".\ie6setup.exe /q:a /r:n" "RunOnceEx.cmd" This will execute during the GUI install portion at T-13 minutes. Note that the path for the command is relative to the $OEM$ directory and not %systemdrive%. This is a good spot to install IE6 because it requires a reboot anyway and so during the first autologon you can call a batch file from RunOnce.Ex.cmd to patch IE6 and OE6, specifically with Q832894, Q831167, Q837009, and while you're at it, Q329115 and Q823559.

Nope! Copy the files from the WS03XP32 of the driver archive and place it in your $OEM$ path and reference it in your winnt.sif file. Also, you need to copy the verfile.tic file from the root of the directory structure of the archive. Below is the directory listing on my unattend install CD: Directory of F:\W2KFFP_EN\$OEM$\$1\Drivers\001_LAN\Intel\PRO100 06/06/2004 11:59 PM <DIR> . 06/06/2004 11:59 PM <DIR> .. 02/03/2003 05:26 AM 12,288 e100bmsg.dll 11/17/2003 04:26 PM 26,626 e100bnt5.cat 06/27/2002 05:53 AM 5,114 e100bnt5.din 10/28/2003 12:14 PM 504,518 e100bnt5.inf 03/04/2003 11:54 AM 145,168 e100bnt5.sys 07/28/2003 05:55 AM 24,064 intelnic.dll 03/03/2003 03:26 PM 118,784 PROUnstl.exe 11/24/2003 04:21 PM 13 verfile.tic 9 File(s) 836,575 bytes 2 Dir(s) 395,878,400 bytes free

There is no setup.ini file in the driver package. Just write up your own setup.ini file. Here's an example for the G200: [SETUP] INF_FILENAME = G200.inf VERSION = Matrox PowerDesk Setup - 5.00.000 LANGUAGE = ENG SILENT = YES REBOOT = NO DISPLAYMODE = 800,600,16,96 RESET_USER_CONFIG = YES RUN_QDESK = NO RUN_DIAG = NO COPY_ALL_DRIVERS = YES LOGFILE = Matrox Setup.log [REGISTRY] User.AGP = 1 Mga.AGPFlags = 04,01,00,00 [TV_STANDARDS] Canada = NTSC France = PAL INF_FILENAME should be the .inf file for your card. VERSION should 5.92.006. The others should be self-explanatory

You need to edit the setup.ini file from the unpacked Matrox driver installs. I unzipped the drivers into my $OEM$\$1\Drivers\004_graphics\Matrox folder and edited the setup.ini file so it would look like this (I am using the Parhelia\P-Series card): [SETUP] PackageName = Matrox Parhelia & Millennium P650/P750 InstallPowerDeskVisible = false InstallPowerDesk = false .NETRequired = TRUE IniFormatVersion=2.0 SILENT = YES REBOOT = NO DISPLAYMODE = 1280,1024,96 RESET_USER_CONFIG_PDESK = YES RESET_USER_CONFIG_DRIVER = YES COPY_ALL_DRIVERS = YES [CO-INSTALL] POSTRUN = Setup.exe /COINSTALL [WIZARD] PCI\VEN_102B&DEV_0527-SUBSYS_0850102B = 2D PCI\VEN_102B&DEV_0527-SUBSYS_0840102B = 2D PCI\VEN_102B&DEV_0527-SUBSYS_0880102B = 2D PCI\VEN_102B&DEV_0528-SUBSYS_1020102B = 2D PCI\VEN_102B&DEV_0528-SUBSYS_1030102B = 2D PCI\VEN_102B&DEV_0528-SUBSYS_14E1102B = 2D PCI\VEN_102B&DEV_2537-SUBSYS_1820102B = 2D PCI\VEN_102B&DEV_2537-SUBSYS_1830102B = 2D [VHEAD] DUALPARH.inf [FAMILY] mtxparh.inf = Parhelia & Millennium P650/P750 I added the lines in the [sETUP] section that begin with REBOOT and [CO-INSTALL] and [WIZARD] sections. If you go to the Matrox Forums and ask for the unattended install documents they will email it to you. The only other thing you need to check is that winnt.sif contains the path to the drivers. The device IDs are taken from the mtxparh.inf file. The syntax will be identical in the Gxx series drivers.

I just tried your settings since I have the same card. No problem here. Successfully installed the driver and XP. Have you run a diagnostic on your hard drive? You may be surprised that it may actually be failing.