jaclaz

Well, check what you have actually done (the result of your "cloning", which is BTW not at a ll a "cloning"), boot from the installation CD and run (Shift+F10 to get to the command prompt) check the existence and size of the partitions (and the "active" status) using diskpart (if I get it right you have a tiny "boot" - what MS calls "system" - partition that normally has no drive letter assigned and a large "system" - what MS calls "boot" - partition that normally gets drive letter C:\ ) then run BCDBOOT: https://technet.microsoft.com/en-us/library/dd744347(v=ws.10).aspx jaclaz

You could make a script to "touch" each and every file, or use "fixed" GMT time on all systems, or - and this greatly depends on the used backup software and on your actual requirements (please read as "requirements" and not as "fancies") allow a "wider" gap for synchronization: https://rsync.samba.org/daylight-savings.html A number of backup softwares can understand the difference and act correctly, as an example, robocopy (since the Vista version) has a /DST switch. Please note how different Windows NT OS versions behave differently (the separating lne is between Vista and 7): https://winscp.net/eng/docs/timestamp http://www.codeproject.com/Articles/1144/Beating-the-Daylight-Savings-Time-bug-and-getting Yes, it is a mess. jaclaz

I don't get it. The Wndows Server 2000 "setup disks" are actually floppies, and you can BTW make them from the Windows 2000 Server install CD (which you should have already): https://technet.microsoft.com/en-us/library/cc938505.aspx The emergency recovery disk is a single disk (still a floppy) that you create from an installed and working Windows 2000. Are you wanting to make a "superfloppy" image with the combined contents of the four setup disk? But WHY (you already have the install CD-Rom or .iso? jaclaz

Without description of context, it is just a 0x0000007b error, "inaccessible boot device" that could be also a missing or corrupted driver and/or a wrong setting in BIOS (ATA/IDE emulation mode vs. SATA or RAID), not necessarily a hard disk failure. jaclaz

This reminds me that both my TV and car are approaching end of warranty ... , though - just like Seagate - the Warranty doesn't cover data anyway. For the record, and just in case, you cannot really-really "clone" a hard disk with drive(image)xml alone, you need also *something else* to take care of the MBR (and of the "hidden sectors") or you will need to rebuild at least the MBR and the Disk Signature: http://www.911cd.net/forums//index.php?showtopic=22984 jaclaz

Good to know (about the patches), talking of serendipity .... Cross linking to: http://reboot.pro/topic/18547-vhd-xp-setup-install-xp-in-vhd/?p=199566 http://reboot.pro/topic/18547-vhd-xp-setup-install-xp-in-vhd/?p=200682 jaclaz

BUT the answer is anyway 42 : http://www.msfn.org/board/topic/43-1=42/?do=findComment&comment=1131594 jaclaz

But there is NO link in the lol probloms , just in case ... http://www.msfn.org/board/topic/0-*/?do=findComment&comment=955858 jaclaz

About Apple news, a good synthesis is here: http://qz.com/822818/steve-jobs-would-probably-very-upset-with-what-apple-aapl-has-become/ jaclaz

@drugwash JFYI: http://clickykeyboards.com/ They removed the logo (that is still available through Wayback Machine): NOT cheap, still ... jaclaz

Add a wild card after the hyphen. http://www.msfn.org/board/topic/0-*/?do=findComment&comment=1131594 If only they could stop "improving" the board ... jaclaz

Let's call that voodoo, and let's go on [1]. jaclaz [1] I won't discuss how not only a different southbridge and disk can change results, but also the phase of the moon or a concurring solar storm may have affected the results of the experiment.

Well, jaclaz thinks that the thing the OP is wandering about is not that much "original", and related info (if interested) can be found with very little difficulties, you know, like looking for them. Namely: http://windowsitpro.com/windows/how-do-i-install-disk-larger-8gb The basic issue revolves around the Int13 extension AND there is also a limitation in the NTLDR, so you will need to use a 2K or XP one (coupled with the corresponding NTDETECT.COM), but - as a matter of fact - it is a non-problem, or - if you prefer - we are talking of solutions in search of problems. Ok, this is not-so-trivial to find : https://web.archive.org/web/20121017215600/http://nu2.nu/fixnt4/ Still, a normal install of a FULL NT 4.0 is around 200 Mb. It is STRONGLY advised (by me, but I simply follow the advice by Gilles Vollant and the actual way NT 4.0 was designed) to install the Operating System in a Logical Volume inside Extended and have a small primary partition for just the boot files (and/or DOS/Win9x). In the real world, you won't EVER *need* the OS volume to be bigger than (say) 2 Gb or so, 8 Gb is much, much more than enough for any possible use of NT 4.0 (of course you keep your collection of DVD's and more generally data on a data volume), here is a complete guide, including the use of the UNIATA driver, that will allow to have also larger than 128/137 Gb/Gib disks accessible: http://nt4ref.zcm.com.au/bigdisk.htm jaclaz

Well, but a .SWM opening (or failing to open) in 7-zip is not a real test of *anything*. What happens using normally imagex (which is what is suggested/explained in this thread)? Also, depending on the OS you can use, maybe DISM would be a valid alternative. Or, you could try Wimlib (namely Wimlib-ImageX): https://wimlib.net/man1/wimlib-imagex-export.html to export the split into .swm's image into a "monolithic" .wim, before despairing/panicking. Semi-random thought, what if you make a copy of PREINST.swm and rename it (the copy) to PREINST1.swm? These are multi-part archives and the inbuilt 7-zip naming convention may play a role in this. jaclaz

Yes/No. Be VERY aware of the possible issues with NTFS version in case you are dual booting with (or however accessing the disk through) a newer NT OS, such as 2K or XP: Also (only seemingly unrelated): jaclaz

More than the ostrich algorithm (which is usually a very good approach, BTW), there is here the possibility (at least according to Ockham Razor ) that simply too many observations are changing the data: https://en.wikipedia.org/wiki/Observer_effect_(physics) It is more a state of mind than something objectively measurable, in a nutshell, if it works, it works (and just leave it working as is or "if it ain't broke, don't fix it"). jaclaz

WHICH PE? jaclaz

transmeta.sys? Maybe crusoe.sys (which is alright in WinFlp and is referenced fine in cpu.inf). I suspect that the issue may be connected with /something else* or with the "strange" way WinFlp is installed. jaclaz

Just for the record: http://www.msfn.org/board/topic/175318-new-forum-how-tos/ http://www.msfn.org/board/topic/175318-new-forum-how-tos/?do=findComment&comment=1120559 Grofluigi has a possible explanation (at least limited to Opera) in the following posts. jaclaz

0x00000019 should be "Bad Pool Header", it is usually connected to programs (or drivers) loading into/scanning memory (Mbam, being an antimalware very likely does this) and leaving the system used memory in an inconsistent state (usually this happens because the process conflicts with *something* else, like - say - a newly installed driver), but it can be also due to "strangely faulty" RAM, so it is a good thing that you checked it and it came out as fine . jaclaz

Well, then it is another bug , different from the mentioned one, possibly limited to the install routine, or maybe triggered by having all four MBR partition table slots "full" with primaries . Lots of people dual boot XP and Vista or 7 using two primary partitions (one for each operating system) using the Mb alignment and something similar has never been reported AFAIK, and - on the other hand - MS has a dedicated tool to create a Mb aligned (actually a 4 Kb which is all that is needed, but however non-cylinder aligned) partition: https://technet.microsoft.com/en-us/library/bb643096(v=exchg.80).aspx jaclaz

The "last loaded driver Mup.sys" hang suggests an issue with the install, that error is typycal of issues with the filesystem, but of course it can also be actually a driver issue. Can you boot a PE of some kind on that machine? (or load the recovery console?) The first thing to do in these cases is usually a chkdsk. This is (thanks Wayback Machine) a good page that lists "common" causes: https://web.archive.org/web/20160407090809/http://www.aitechsolutions.net/mupdotsysXPhang.html The processr.sys is anyway not the issue, at least in a backup I have of the Futro it is the same file as the "normal" XP SP2 one, like the one in WinFlp. jaclaz

Naah, it's the same setting, the difference is that knowing directly the involved Registry key allows you to do it also when offline (let's say an unbootable system), by directly editing the Registry from a PE or another bootable instance of the OS. BTW it can also be reached through F8 "advanced settings" when booting. jaclaz

Well, just in case, there is a setting that allows you to have the computer actually STOP on STOP errors, unlike the "Autoreboot (before anyone has time to read the STOP ERROR. let alone take a note of it)" action that the good MS guys in their wisdom set as default in XP and later. http://www.pctools.com/guides/registry/detail/229/ jaclaz

I used to have a Fujitsu Siemens Futro (220 if I recall correctly) with a Transmeta 5800 and it worked nicely with XP (SP2 for the record). The POSREADY 2009 IS EXACTLY the same as a "normal" XP, so no issues there that I can see, JFYI: WinFLP may be another thing. Which EXACT, SPECIFIC BSOD STOP ERROR do you get with WinFLP? Very likely it is just a matter of a missing driver (that should be possible to "add" to the install). jaclaz