Alanoll

just do a search (HEX search , not string or the other one) for 00 00 00 00 15 1A 20 00 46 46 46 00 D2 3E 2D 00 01 and that should get you too it. Also remember that when you edit the pallete..... the format isn't RGB but BGR with 00 spacing each entry. If you don't find that string above, then you're trying to mod an already altered one, and I suggest you get a fresh copy from I386 or so. Also be sure to use the right kernel for the right system. (Single Processor kernel vs Multi-Processor Kernel)

he search ASPI

Google for a program called Boot Editor. Copy the ntoskrnl.exe file in the boot editor folder. Start up booteditor. It should display all bitmaps correctly. It will also save the bitmaps properly too (I think anyway)

Only time I've had that error is when I tried to put the wrong SoundBlaster drivers (wrong version). You could eliminate the possibilities. Do a test without Drivers. Do a test with Regtweaks. So on.

Bravo

that's the ONLY website I've seen that would even come close. You're going to ahve to use some deductive reasoning and find the bytes and change them yourself based off that website.

the marker files don't belong to the OS though, but rather the CD. But the files aren't in the wrong place. Theoretically, they belong to the root of a CD with Microsoft files on it, so they are in the right place. and the file you want to edit is layout.inf and txtsetup.sif look for the section [sourceDiskNames] or something like that.

next time, do a search. http://www.lvllord.de/index2.htm

Didn't look very hard did you? http://unattended.msfn.org/xp/finish.htm the first section regards what you want....

the ATA card is NOT included. An older ATA66 driver is still included. For drivers to be included, the manufacturer MUST send the drivers to Microsoft. As for a listing....good question. drvindex.inf perhaps?

Unfortunately that was the cause of FFA's error though.....but alls well

I've only seen this problem in the nLite forums (about the driver signing anyway). Did you use nLite to slipstream the servicepack? If so, .98.4 ,.5 or so had a problem with causing it. Though I could have sworn DriverSigningPolicy in winnt.sif would fix it (workaround anyway). If you did use nLite to slipstream, if may be better to redo it with the latest one....

I miss ONE post.....can't believe I haven't seen this post yet..... I am ashamed..... But I've been busy as of late with Uni starting up, and I've got to get that Winamp MSI out the door.

don't use OEMSETUP.EXE Search for the previous post

It was said that hotfix's specifically, Type1 like ones would be able to....or more specifically, those using update.exe v4 or somewhere around tehre.

if he saved his wpa.dbl file, he could move it to his new computer and it would be activated.... but that's about it

@j4ever now seriously, why would you repost a link after I said not to? I don't care what neow1n does, or what other sites do. Untill it's on the Microsoft servers to download.....it could be considered illegal. And when it is on Microsoft's servers, link to it, and not other sites. And Microsoft doesn't let people "find" it to reduce the strain on their servers. They didn't for SP2. When SP2 was leaked, it was because of the people who had the MSDN subscriptions and access to the Beta site.

Link Removed ~ Alanoll Technically, Untill Officially released, links could be considered illegal

All those annoying new things, especially that "Open FIle Security Warning". I wish they made it easy to turn it off....then I'd have no problems. Or a way to ask if a program doesn't run (breaks the new Microsoft regs) then ask if you still want to run it....

On the skipping of product key screen, last I saw Microsoft put in that limitation on purpose. So it's not a broken CD. I personally think people are starting to make nLite look like the end all solution. Nothing beats doing it by hand. As for more advanced Windows 98 stuff, there is ALOT of information on it and usage and such on the microsoft website. As well as slipstreaming drivers....

My instructions needed an understanding of the basics of kernel editing. Seeing as you didn't understand, I"m guessing your DON'T have that.... Check the cometics thread for instructions.

Let's not forget the obvious, that if you're instlaling from CD, and booting FROM CD, then $OEM$ needs to be in the root of the CD. However, you can use CMDLINES.TXT like a command prompt, but they need to be external commands (regedit , applicaiton installs , cmd.exe)

OT: It's very good to annoy a teacher though. And if you time it right with everyone else in the room, you can get a beep to travel around teh room Not that I"ve done this before...... But it's a pitty I didn't get here sooner. Blast, need to work on that.

or it may cause some problems elsewhere taht are unknown.... but yes, the UIHost needs teh FULL path, and if you specify GinaDLL then the Welcome screen is disabled, so you can't use both. As for the naming, if you're using UIHost, the name legth really doesn't matter. Mine is (LOTRLogonScreen.exe) and it works fine

try commenting out the applications, browsing through, I would recon it's either MSN messenger or the XML parser. Try commenting both out and see what happens.