rockie

thanks for comments... flushing meory/perfmon & etc. now i need to ask what i should use to " flush memory ". thanks. ^^

my computer is still running, since 5th Dec. for some reason, no more application can be launched when this happening, all double clicked application's memory usage is like 2,932k in task manager. is there any ways to keep windows xp fresh for a long long time ? -------------------- windows xp sp2 xp2500+ 256mb via kt880

isn't it windows server 2003 x64 edition Just with windows xp x64 name tag ?

above method definitely works, it was joliet problem. i changed it to standard iso, it worked. but my other burnt cds are joilet. nvidia driver should work like this, also i have integrated nvidia's and no loading problem, this cd may work with nforce based mainboard.

I've modified x64's dosnet.inf and txtsetup.sif as I did with 32bit version. and placed iastor.sy_ in amd64 folder / full copy of iastor.sys & inf in $oem$ and in winnt.sif, i added correct path for driver location. While x64 installation cd is loading, iastor.sys could not be found and it's over. With x64, something more should be modified ? DOSNET.INF [floppy.files2] d1,iastor.sys [files] d1,iastor.sys [forcecopydrivercabfiles] iastor.sys ----------------------------------- TXTSETUP.SIF [sourcediskfiles] iastor.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_8086&DEV_xxxx = "iastor" [sCSI.Load] iastor = iastor.sys,4 [scsi] iastor = "Intel xxxx"

maybe 4_, not 3_... [sourceDisksFiles] fasttx2k.sys = 1,,,,,,4_,4,1 ulSata.sys = 1,,,,,,4_,4,1 and create $OEM$/$1/xxx and specify xxx as OemPnPDriversPath in [unattended], WINNT.SIF & place PDC378 driver files in xxx & *.sys in I386 ---------------------------------------- OemPnPDriversPath=xxx * $OEM$ should be created in root, where I386 folder is located.

Those progs are bigger than driver files, I guess adding driver files is easier.

Oh, DOSNET.INF is for Winnt32 based installation. Thanks However, I don't know why this problem happens with SiS Raid Controller. I've tried to uninstall driver and restart windows or reinstall different version of driver. But still SiS Raid Utility says, NO SiS Raid Controller.. hmm.

I have modified DOSNET.INF & TXTSETUP.INF and added sisraid.sy_ into I386. and OemPnPDriversPath in WINNT.SIF for WXP SP2 Unattended installation. So installation completed on SATA RAID 0 and 655FX+SiS964 mainboard. But there seems a problem, SiS Raid Utility can't identify SiS964 Raid Controller, so does Raid configuration. This problem doesn't happen if SiS Raid driver is added via floppy with normal WXP SP2 installation CD. Does anyone know what would cause this problem ? And is it really necessary to modify DOSNET.INF ? I have tested Unattended installation with modified TXTSETUP.SIF only, there seems no problem at all.