i posted an update to clarify something in the morning and i just noticed that no one had replied and thought i would check again... its not like im replying to my own post with "^^BUMP^^" every 30 minutes.
yup.. and i think its screwing with the windows firewall too. i enable it... then after a restart when NAV loads.. it disables it and windows starts complaining about it. i could be wrong and something else might be at fault.. but right now NAV is looking like the cause.
they said to check back here (http://service.symantec.com/xpinfo) august 10th for a patch.. no patch and its august 10th.... symantec knew what was coming for a long time now.. why didn't they have a patch out when SP2 was released... or is there one and im just overlooking it.
just delete the svcpack.inf file altogehter.... only problem is... now im getting usbehci.sys corrupt errors when i boot to the cd.... someone suggested i change the case of the filename to upper case and i tried that but still nothing.
also...... this is with an OEM cd. i tried it with a volume license CD and it worke perfectly. however, i don't want to use my volume license on this machine. OEM CDs can be slipstreamed and made unatteneded right?
awesome.. i just downloaded the case changing tool and changed the case of everything in my i386 to uppercase and im reburning it now....... <fingers crossed>
after pressing any key to boot to Cd.. while its loading files it gives that error and will not allow the installation to proceed. here is what i did. copied contents of a windows XP pro (non sp1) cd to c:\XPCD deleted c:XPCD\i386\svcpack.inf AND c:XPCD\i386\svcpack (fi i didn't delete this it complains that I can't integrate SP2 because the intsallation already has updates integrated..... the hotfixes in the svcpack.inf file. added my own custom winnt.sif & unattend.txt file to the i386 directory windowsxpsp2file.exe -integrate:c:\XPCD ran CDImage Pro (XP Pro) to make a bootable ISO from the contents of c:\XPCD used nero to burn that ISO to a CD. i've tried it in two different machines and still get the same error.... any ideas?