Denney

@Alanoll: I've modified both and it seems to install the MP one still (but Windows still won't boot because it's not a MP system). I know I'm hexing the correct places because if I replace it manually, all works fine. @MHz: Doing that works. But Windows has a tendancy to freeze afterwards (probably because Windows was installing the MP version). Personally, I've just created a batch file that will replace after first boot (using my software selection program). That way, it's also selectable during setup so if I have another boot screen I can install it instead (using update CDs). So, I've made my own workaround for it and even found a bonus in using that workaround. Thanks for your help anyway guys.

Has anyone been able to find the following text (Can't find it in SYSSETUP.DLL or WINNTBBU.DLL): "building file list" "performing configuration" "completing installation..." Anyone?

OK. Heres my info... 1. I'm using VMWare and it's NOT hyperthreaded or multi-processor. 2. The kernel will be replaced after T-12 aswell (tried replacing it in CMDLINES but got overwritten). 3. I'm definately modifing the single processor versions (NTOSKRNL.EX_ and NTOSKRNL.EXE). 4. If I don't change the position of the progress bar or the color palette it uses the single processor kernel. Modified Palette or Progress Bar SingleProcessor Kernel MultiProcessorKernel No Yes No Yes No YesSo, you see the problem now? I have NO IDEA why it replaces the single-processor kernel with the multi-processor one. @Big poppa pimp: I don't know why I'd have to modify EVERY kernel on the CD when Windows will only boot with the single-processor one.

Nup.. Didn't work. I've replaced both the NTOSKRNL.EX_ file in I386 AND the NTOSKRNL.EXE file inside DRIVER.CAB. I could modify the NTKRNLMP.EXE files but that wouldn't work as my computer isn't a multi-processor computer. Windows just freezes on bootup with the multi-processor kernel. I don't know WHY it is using the multi-processor version of the kernel. I hope someone else is having this problem so maybe we can fix it.

Yeah. I just read about the one in DRIVER.CAB (combined DRIVER and SP2.CAB). I'm testing it now. Just seems strange that it replaced it with the multi-processor one. :S

OK. I don't know if anyone will be able to help me with this but here goes... I have modified my SP2 bootscreen and placed the NTOSKRNL.EXE file back on the CD (modpe'd and compressed). The modifications I've done are, replaced main + progress images, changed palette, changed position of the progress bar (using: http://www.msfn.org/board/index.php?showtopic=24286). After text-mode setup, the computer boots with my bootscreen and starts setup but once setup is finished, my computer restarts and starts loading the ORIGINAL windows xp boot screen and freezes on startup. I looked into this in safe mode and found out that the NTOSKRNL.EXE file in system32 is actually NTKRNLMP.EXE which is the multi-processor version. Now, I don't have a multi-processor system. If I just replace the images and do nothing else, it boots fine. Can anyone explain this odd behaviour to me? Note: I can replace the NTOSKRNL.EXE file AFTER boot and it works like a charm. For some reason, Windows setup is replacing the file.

I paid $25AUS for a PS2PC converter called, funnily enough, PS2PC created by an Australian company called TruBlu. You can get the converters for cheap enough and it's a lot easy then making your own. USB is definately the way to go. Anything else and it's really to slow to be any great use.

because we like to do it the hardway!!!

The same thing happened to a place that used a logo that was too close to the Google logo (had nothing to do with Google, just happened to use the same colors, in the same order and the same style). They lost ofcourse. This is the same thing really. Big corporations are really taking this copyright thing to far.

Personally, I have to agree with Microsoft on this one. I mean the font, words look like Microsoft's logo... I mean, demading him to give it to them is a bit much but to me, whoever owns that www.mocosoft.com site was asking for it.

Have an edit for you: 00 00 00 00 15 1A 20 00 46 46 46 00 D2 3E 2D 00 01 65 53 00 05 35 B2 00 7E 7E 7E 00 00 92 89 00 FC 7F 5E 00 20 6B F7 00 FF A6 8D 00 04 DC 8E 00 1B BC F3 00 BC BC BC 00 FC FC FC FF FF FFshould be changed to: 00 00 00 00 15 1A 20 00 46 46 46 00 D2 3E 2D 00 01 65 53 00 05 35 B2 00 7E 7E 7E 00 00 92 89 00 FC 7F 5E 00 20 6B F7 00 FF A6 8D 00 04 DC 8E 00 1B BC F3 00 BC BC BC 00 FC FC FC 00 FF FF FF Note the last few bytes... FC FC FC 00 FF FF FF.

Heres the first version of our MSA setup screen (not available for download yet). We still need to change the current item's text color and the progress bar color. We're also adding static text to the background (using the text in WINNTBBU.DLL causes the image to look jaged around the edges of the text box). Setup Screenshot

Sweet... Thanks. I'm trying this now... will update with some more information. Edit: I seem to be having some problems with file copy errors... I've added the files to "DOSNET.INF", "TXTSETUP.SIF" and "LAYOUT.INF". I've modpe'd them and compressed them. I don't have any more time at the moment to test this further. I'll try later on today (hopefully).

Actually, SFCDisable is correct for a normal install of Windows XP with the original sfc_os.dll hack. If you use MY hacked sfc_os.dll file, you need to add SFCSetting. Difference being that the original hacked sfc_os.dll file disables WFP after setup is complete and mine disables it during installation as well.

I think this is it: HKCU,SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced,TaskbarGlomming,0x00010001,0x00000000 or if your using reg files: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced] TaskbarGlomming=dword:00000000

You a lucky person... you were smart enough to follow the guide properly... Well done.

For anyone else who has this problem... The name in your sysoc.inf file BEFORE the = sign MUST be the same as the heading in your component INF file. eg. sysoc.inf: OEAccess=ocgen.dll,OcEntry,oeaccess.inf,,7 oeaccess.inf: [Optional Component] OEAccess [OEAccess]

@Metzen: That would be a good idea. I'd like to look at the differences.

Just updated with version information and some other new notes.

@GhettoChild: What do you modify to get wmp10 to install?!?!? Do you change SYSETUP.INF? How do you get your slipstreamed version of wmp10 to install?!?!?

@Ghettochild: I know you'd need to change SYSSETUP.INF, that's why I asked you how it actually installed. You said it installed when setup ran... I just wanted to know how because setup would need to call the INF file at some time.

The automatically generated computer name is totally random and partly based on your workgroup or domain name. You will need to set your computer name.

@Ghettochild: Just looked at your bat file and I'm wondering how Windows setup knows to call WMP10.inf? According to SYSSETUP.INF, it calls WMP.inf and not WMP10.inf. How is this installed exactally?

Well, InstallHinfSection doesn't return a value so "Sub" is correct... With or without Auto it still won't work. I've tried for about 3 days on this so I'm going back to calling "rundll32.exe".

@HeartsOfWar: 1. I was using that before but I want to get rid of the need to call external applications like that. 2. That is what I'm doing but I don't seem to sending the write values. @crahak: Thanks. Basically, what I need to is, what is the Visual Basic equivilent (sp?) of C's "PCTSTR"? How can I pass the equivilent (sp?) of a "PCTSTR" in Visual Basic .NET? At the moment, the function call works but then setupapi gives a message box saying "Installation failed". The input string is CORRECT and using the exact same input string but making an external call to rundll32 works. If only it was a LPTSTR, it would work... How the hell do I convert a PCTSTR? Thanks for your help though.