Takeshi

Depends what you mean by connecting. File sharing/remote desktop/RA/remote registry etc.

I don't see how bootvis helps. http://www.microsoft.com/whdc/system/syspe...ot/default.mspx

That's what I meant. The NT boot files (boot.ini, ntldr and ntdetect.com) although needed for booting are not part of the "bootsector" technically.

Win XP Pro (but not HE) supports dynamic volumes (but do take note of what's been said above).

You can do it with VBS using ADS_UF_DONT_EXPIRE_PASSWD as the constant. e.g. for some pointers: http://www.microsoft.com/technet/scriptcen...04/hey1202.mspx There're quite a few on Google, this one e.g. http://www.markwilson.co.uk/blog/2004/09/s...-expiry-for.htm

The crux of the matter is: how did you put the old OS from the old HD to the new HD? You said you put the "data" on the new HD but didn't say anything about the OS transfer itself. Booting an OS is more than just using the boot sector. You need the partition table, MFT, NT loader etc. Are these there and intact?

Software still relies on hardware so it's futile to expect that it will miraculously solve the old hardware problem.

I'd try: [RegionalSettings] LanguageGroup = 1 SystemLocale = 00000409 UserLocale = 0000041d InputLocale = 0409:0000041d The SystemLocale (for non-unicode programs) and UserLocale (for formatting standards) are not relevant to your specific query.

You probably need to do this too: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Toolbar LinksFolderName Delete the Links (or whatever name) under Data, leaving it blank

Thanks Mr Snrub for testing this. I'm still puzzled about this: local policies and network logon in XP Pro?

This is a known issue for some programs in non-English OSes. The easiest workaround is to rename the filename to the default language of your OS. Another method is to try (but no promise it'll always work) setting the system locale to the particular language of the filename in: Regional and Language Options > Advanced > Select a language to match... The above could also be done by MS AppLocale. http://www.microsoft.com/globaldev/tools/apploc.mspx To clarify the extended character issue: what you get when you type (with the Alt + numeric keys) would vary depending on the default codepage, so what you get with En would not necessarily be the same in other language OSes.

regedit32.exe doesn't exit.

That's a bit odd. You don't have to be the built-in Administrator to do that, just any account with administrative privileges. If you don't know what you own account is, go to Control Panel > User accounts. (You won't be able to access Local Users and Groups MMC snap-in in XP HE). If you have XP HE, go to Safe Mode to access the built-in Administrator acc.

Logon as admin and loading the specific user's hive to edit it might be a workaround instead of logging into each user's account.

There's a policy in Secpol.msc: Local Policies > Security Options > Network Security > Force logoff when logon hours expire I don't know what or where exactly this will be applicable (domain?), as there's no explanation. But then "Local" would imply local computer, wouldn't it?

or this: http://www.msfn.org/board/index.php?showtopic=44972

Just make another XP CD using your existing uA CD, but replace winnt.sif with a blank one.

1. The entry requires BrandIEUsingUnattended = Yes to be there. 2. more on auto~ v. repartition: http://www.msfn.org/board/index.php?showtopic=59315

[RegionalSettings] SystemLocale =

Q1. Looking at your boot.ini, you're either booting WinPE or RC but not both, depending on the version of txtsetup.sif. By design, C:\WindowsPE\minint won't work. cmldr looks for minint and not WindowsPE\minint. I don't know if modifying it would work. Why not try it? Q2. Isn't it when it's connected to the mains it always uses mains power?

download properly? http://support.microsoft.com/default.aspx?...kb;en-us;831426 http://www.winguides.com/registry/display.php/907/

Why not use /integrate instead?

Alerter and Messenger services are disabled by default in SP2, so why take the redundant step to include them again (Disabled) in system tweaks?

If there's only one account shown on the Welcome screen and that acc has no pw then it won't just stop there and wait for you. That's by design. And why would you want it to stop there anyway if there's only one account? Either create a pw or another account.

That doesn't look it's done a chkdsk. I don't know why volume is dismounted. Have you looked in diskmgmt.msc? Or do chkdsk offline, in Recovery Console. Offline means DOS/Recovery Console/WinPE, not Safe Mode. So try deleting the file offline.