Alanoll

if it's via commandline, I believe setup uses layout.inf not txtsetup.sif

Both are yes's. But when I get time.....darn school starting up again....

I personally, don't like using Winamp for my video, so....that's gone. And I prefer classic skin, so Modern is gone..... Just little things. Giving people a choice

@battleangel3222 Please behave with mutual respect. This thread is in the Applications Switches Forum and not the Unattend FOrum. If this were in the Unattend forum, there is no need to make a post such as yours. You could remind him it's the wrong forum, and then point him in the right direction. Sometimes accidentally post in the wrong forum simply because they have many windows open and they loose track. When the realize it, they let a mod know, and we will gladly move it.

ummm...joke?

so it is agreed then? use the beta Winamp 6.0? I'm finally back to my lab, but I start classes tomorrow....we'll see what happens. But atleast if I get free time I can atleast start

A search will bring up almost all of those programs. Or unattended.msfn.org as for using VirtualPC, it's the EASIEST one to use. Just follow the wizard to setup of the virtual machine, start it up, load up the ISO (second drop down menu at the top or so)

Well, considering there is usually a default ATI driver loaded from the XP source, it should still work.....assuming you check for the file that is the right one. But when newer cards come out then there might be problems if you don't use OEMPnPDriversPath to instlal the driver first.

I'm afraid I'm personally under the impression of not helping people that openly admit to having pirated windows. If you dont' tell us, that's one thing, but.....geeeze....\ And for the record, %CDROM% won't work in GUIRunOnce as it's not defined. And the path is wrong, because $OEM$\$1 is copied over to %systemdrive% There is nothing wrong with %systemdrive% being C: as that's the SYSTEMDRIVE. %systemroot% is C:\Windows typically.

I personally find it to be just fine. Simplistic so it's not confusing, and hopefully not that much more load on the server. But the final decision is determined by xper most likely.

Atleast you're past that one week mark.

it all depends on what you're trying to do and how you're installing your applications. If they all run off CD, then take it about at T-14 , otherwise it won't matter as if you change something you'll need to change the file in the snapshot.

I got quite a few going to waste, they just keep giving them to me..... so the rules are what? over 2500 posts? j/k so yeah....here's some more.

look on your current system with Winamp currently configured. Go to %windir%\winamp.ini .... copy that file in your install routine and your WON'T get that registration page

What you could have done.... is open up the bitmap in Photoshop or something, write down the hex values, flip them, and then in the new kernel locate the strings for the ORIGINAL pallete, and just overwrite. Same with the progress bar. You just need to know the position to put it.

I sure hope so. If not it would only take a few hours to redo all of it...the problem is, I've been away from my main system for the past few days, and I don't have InstallShield X installed on this computer. And I honestly can't believe people are really expected teh MSI after 3 days the original was released......

using ntoskrnl.exe from themexp.org is simple. Open up the downloaded file in ResourceTuner or ResHack and save the bitmap. Then open up your kernel, and do what you do with other images. As for editing the palette, that's the simple thing. I never muddled with the progress bar though.....

so someone else can fix your kernel?

this site may prove useful http://www.geocities.com/thejjoelc/XPbootcolors.html#pal

new.inf should theoretically run about T-13 or just alittle sooner. I forget exactly when. At which point, it imports the new keys from XP and DefaultInstall. If those are again RunOnceEX keys, then they will launch their install upon restart, where as if they were normal registry tweaks, they would be imported then. As far as I can tell, browsing through the original INF on gosh's website, [13min] is never executed using XP or DefaultInstall in the INF call. Except for when in the other secionds there is an RunOnceEX call to the INF using Post [strings] is executed whever the INF is used. It's just declaring variables like SET in a batch file.

whoops yeah, they're supposed to be in system32, not just windows. My bad....

don't worry about the snapshot business. Unless you know what you're doing it cause more problems. and yes the file should turn out different, as long as your only run the file ONCE.

yes, do start from SCRATCH again (ie. use VMware or VirtualPC and reinstall the OS reformating the virtual drive) It doesn't. That's what the batch file gets around. Just disregard the hyperthreading fact. Your files look fine (took 17 minutes to download), just reinstall the ENTIRE OS before saying it doesn't work. The batch file also allows that if you use the SAME CD on an Athlon system and a P4 (or virtual system) then the bootscreen still gets applied correctly, using the proper kernel.

oh my..... that's.....just bad..... [boot loader] timeout=0 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional" /fastdetect /kernel=dualkrnl.exe multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect If this test is done in VMware, the result should resemble THIS. How are you testing the batch file? are you just double clicking it in your current install or something (won't work)?

wat else can i do? well, a simple search in your virtual system would tell you. It's in C:\boot.ini (figure out how to copy it) As for other ways, you could ahve taken a snap shot, then started from there each time, instead of going through the whole reformat, copy process.