Everything posted by n00b
-
Sysprep factory mode
Is it OK to run sysprep -factory command during the T-13 stage of XP setup? Basically I want the system to go into Factory mode right after XP setup
-
PROB | ATI DVD-Decoder
Are the decoder files supposed to be in the common files folder? I got it to silently install by using InstallShield X and modifying the installer, SO SWEET AND EASY I run it like this for those interested: msiexec /qb /i atidvd.msi reboot=reallysuppress and there is a custom execution script that aborts the install when you try to install it silently, all I did was delete that .. and now it installs EDIT: oops... cannot repair/modify/uninstall DANG
-
PROB | ATI DVD-Decoder
How did you get it to install? All mine does is spawn the ATI Cd checking utility until no end
-
error with sysdiff and winxp
grab a copy of that file from a windows 2000 machine it will work in XP
-
XP SP2 file structure/file size needed
Hey can you give me a listing of the files in the I386 folder as well attached to your next post THX
-
XP SP2 file structure/file size needed
And from here it gets more confusing. Some people with SP2 slipstreamed have a 10100, 60100, and a 70100 folder. Yours doesn't. When I slipstreamed SP2, it just deleted the manifest file from the 10100, 60100, and the 70100 folder. (causing setup to crash of course) WTFWTFWTF
-
XP SP2 file structure/file size needed
Professional. kthx this slipstreaming process is a pain in the a**. I wasted 2 CD's now WTF
-
XP SP2 file structure/file size needed
Can someone give me a file listing and file sizes of the ASMS folder of your WORKING slipstreamed SP2 CD? Thanks
-
ATI Catalyst Drivers
What's the difference between the Windows 2000 INF and the Windows XP INF file? Is it OK if XP uses the 2000 INF files? Can I remove the Windows 2000 INF file and not experience problems during setup?
-
Windows SP4 and included version of MSXML
Win2k comes with XML 2.5. I think it might have xml 3.0 sp2 as well..........................................
-
Has a valid key slipped through?
Welcome to many moons ago.
-
Save HOURS of time from making ur cd
Here's what I do: I just rip out the hotfixes and put it my unattended installation. It doesn't come from MS? Oh then where else do we get hotfixes! Besides if a 3rd party modified it, the digital signatures surely would be invalid
-
Save HOURS of time from making ur cd
First thing: Make your own DB. DB editor's coming soon Second thing: That's why there's UltraLite and Lite edition.
-
Save HOURS of time from making ur cd
MSN Plus! contains adware, but if you look at the switches it's specifically set to NOT install it. AutoPatcher XP has a Lite and UltraLite version, you can use it if you don't want the 3rd party software (which is pretty much useless IMO) and the regtweaks (again, unneeded IMO)
-
Some questions
Anyone know what the purpose of these commands are for? (unattend.txt) OriTyp = "5" OriSrc = "C:\I386" floppyless = "1"
-
German version for WMP9_MM2_ENU.exe ?
Can you register for OEM.MICROSOFT.COM even if you are not an OEM and you are under 18?
-
EVERYONE READ!
Maybe to zealots, not to Linux itself. Yep, that's what I meant
-
Invalid picture
I don't know ... I run the EXE and it says "invalid picture"
-
Invalid picture
I'm running some tools like Flash Renamer in WinPE and they all return an error saying "INVALID PICTURE". Help?
- EVERYONE READ!
-
How to *properly* provide source files...
woah, ignoreme
-
Digital signatures
Nope, that had nothing to do with it I narrowed down the problem and it INDEED is a conflict with the Windows XP hotfixes. I have 62 of those installing
-
Digital signatures
It indeed was the hotfixes!
-
Digital signatures
Hmm, a search on Dell|Talk reveals that it may be caused by a hotfix, crap got a lot of work to do to find that bugger
-
cmdlines.txt error
"05/02/2004 00:20:06,d:\xpsp1\base\ntsetup\syssetup\log.c,133,,Setup was unable to execute the commands in $OEM$\OEMFILES\cmdlines.txt. 05/02/2004 00:20:06,d:\xpsp1\base\ntsetup\syssetup\log.c,133,,Error 05/02/2004 00:20:06,d:\xpsp1\base\ntsetup\syssetup\log.c,133,,: 05/02/2004 00:20:06,d:\xpsp1\base\ntsetup\syssetup\log.c,133,,Setup was unable to execute the commands in $OEM$\OEMFILES\cmdlines.txt. 05/02/2004 00:20:06,d:\xpsp1\base\ntsetup\syssetup\log.c,133,," These errors appear in the Windows set up logs in the C:\WINDOWS folder. What I don't get is why are they being called. I do not have such entries listed in the original CMDLINES.TXT. Help?