Takeshi

Why can't you? You renamed it but it should still be there. If it isn't then something has gone seriously wrong.

So z is RAMDrive? What's in disk0_1.txt and disk0_3.txt?

I forgot to say that Windows XP can increase the PF even when you've set it to a fixed maximum. It happened to me more than once before. It doesn't have to crash. So it depends on the program (it was VMWare running at the time). So it's not the end of the world when you set the PF too small. It will cause a slight delay when Windows enlarge the PF but that's all.

Simply because once you logon in Safe Mode using the Administrator account, you can go to User Accounts to create a new account. It's just that simple. Unless you know how to do the same using WinPE/BartPE by modifying the SAM, it's a non-starter.

That's I believe, how Incroyable HULK lists come about and that can be relied upon. You shouldn't need to add older hotfixes that have since been replaced with newer versions. There're also updates that aren't security hotfixes, but merely optional software updates. You can zip the file before uploading.

Every so often someone resurrects one of the old PF threads here. It seems the flame will never extinguish. What I can't figure out is, why does it have to be a single setting that applies to everyone in the Universe? Why do we have to be so dogmatic about it to the point of vigorously defending our belief? It's all very well what the Memeroy Manager is supposed to do but does theory always apply in practice? Is the PF need for someone who only uses the computer for emails and internet the same as another who uses Photoshop and Premiere? If only system managed size will do and anything other than that will crash the computer, then why does Windows let you customise the PF in the GUI or via regedit? Does that suggest that most of the time it will be alright if you customise the PF one way or another, because the need for PF size is only moderate anyway for most users? Is there any hard objective scientific evidence that one setting is the best?

The presence of $OEM$ dir does not mean the source is necessarily OEM. It just means there's extra stuff to be put in. Whether the source is OEM is determined by other means. Wpa.dbl needs to reside in system32 eventually but this method of replacing it no longer works after XP SP1 as testified by many users, so there's no point pursuing it.

Managing Windows XP Service Pack 2 Features Using Group Policy Windows Firewall

As the CD loads, after the messages Press F2 and F6, it starts copying files to RAM. I'd not be so confident that it's not a HW problem, esp. RAM. Linux and W2k require less RAM than XP.

You can put your hotfixes on the 2nd CD and call it during install. This qu should be in the UA Windows forum (and in fact already discussed there).

I get the impression that there's no universal solution that applies to ALL the updates and hotfixes. KB890830 (malicious sw removal tool, a scan really) is different as it writes to a different reg key but it can be fooled (already discussed elsewhere). KB905474 needs the current legitcontroll.dll, wgalogon.dll and wgatray.exe at least. I've since found there're more registry keys involved. Perhaps it'd be more helpful at least to post which KB works using your method. I've also noticed that the yellow shield in the Notification Area notifying you of updates can behave inconsistently, when it says you need this KB even though you've already installed it, and when MU website says you don't need it. So it might confuse the issue during testing.

Looks promising, thanks. I think it would work. Awaiting your testing...or when I get round to doing it...

Trying cd to WINDOWS first. Don't know if adding the /A would help. Since you want to uncompress all of C, you can probably do it in the GUI. R click C > Properties, untick the box [ ] Compress drive to save... Your DELL PC didn't come with OS CD, whether it's XP Pro (it should) or MCE (don't know about that)?

It looks like you deleted the only other account apart from the built-in Administrator account, so in normal mode you have no account left to logon - and remember XP HE won't allow you to logon to the Administrator account EXCEPT in Safe Mode. You have to have another account to logon in normal mode in XP HE. In XP HE, the built-in Administrator account can only be accessed in Safe Mode. It cannot be deleted. So it can't be this account that you deleted. By default it has no password. If you set a pw you should still be able to logon in Safe Mode. So try that. Keep things simple, before rushing to boot with WinPE. In XP HE, there's no gpedit.msc.

It is possible that during the process of compression, those Windows files normally protected by WFP were included. It strikes me that it's never a good idea to compress OS files.

You're right about the blank value. I don't quite understand this bit: because notepad and cmd aren't in the Program Files dir anyway. Also, HKCR\Applications\ is the same key as: [HKEY_CURRENT_USER\Software\Classes\Applications\ It's just the way regedit displays it differently.

We (or perhaps only SMs) were allowed to do that before for XP OPK... http://www.msfn.org/board/index.php?showtopic=56488&st=0

I've not tried installing BartPE, but installing MS WinPE/XP SP2/Recovery Console on HD worked for me. http://www.msfn.org/board/index.php?showtopic=62321 From what you said, the method is similar but not identical.

Success Basically: Used ImgBurn 2 to build the iso using existing authored files on HD, chose the layer break manually (probably using existing ifo), saved iso and mds, used ImgBurn to burn mds. DVD DL played in Pioneer DVR111D and standalone ARCAM DVD player. Thanks again to everyone who helped. ================================ ADDENDUM Further improvement: If you have the original DVD, load it in the DVD-ROM and open ImgBurn, go to Mode > Verify. On the R it'll show you exactly where the layer break occurs (right at the bottom). Something like: Then you can compare this with what shows up later during Build and in addition, use IfoEdit to have a look at the corresponding PGC and Cell IDs.

Many thanks for the updated script. Have you considered, rather than having a selection of sizes, how about allowing for a custom specified size on the spot, if that's possible to do (write to a temp diskpart.txt)? Just wondering...

Does it boot in Safe Mode? something to do with EVP? Your query is really "failure to boot after installing SP2", rather than "cannot install SP2".

Look here.

If the above doesn't work a corrupt HD boot sector (not necessarily the MBR as such, because GRUB is still there) is also plausible. Perhaps your HD is faulty. Go back to the basics. Check the BIOS boot settings again, including the SATA boot options. Ensure there's nothing in the floppy drive. Do a repair installation or start all over. Do a check disk.

1. The process also works for XP HE. 3. Make the iso first, then use the iso as the CDROM.

You can also have: $OEM$\textmode $OEM$\D (or other drive letters)