Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


glnz

Member
  • Content Count

    517
  • Donations

    $20.00 
  • Joined

  • Last visited

  • Days Won

    3

glnz last won the day on December 18 2018

glnz had the most liked content!

Community Reputation

57 Excellent

About glnz

  • Rank
    resident supermegaüberhyper-ultraparanoid

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hel-LOW-oh? Anyone home? Askwoody has this post, which predicts embedded support for Win 7 for another two years. https://www.askwoody.com/forums/topic/september-patch-tuesday-rolling-out/#post-1949416 Is the "usual gang" of tech wizards here working on a POS-type hack? Look, Dave-H, I know you love Win 98, but lemme have some support here, man.
  2. Jaclaz - For some reason, the second file-link I saved from HDHacker is wrong. The Physical Drive (MBR) is NOT the same as the Logical Drive (Boot Sector). Physical Drive (MBR) is here: https://my.pcloud.com/publink/show?code=XZKsRJkZxC2C0P2DmczG1FsuPxhfH8kvIncV Logical Drive (Boot Sector) is here: https://my.pcloud.com/publink/show?code=XZNsRJkZCNpTxvRh6iF3RTd8iRyqoJYPqxg7 Please confirm they are now different. When I "Compare with loaded", then "Logical Drive (Boot Sector)" is the same as loaded, but "Physical Drive (MBR)" has many differences from as loaded. New thoughts? Thanks. is NOT the same as the Logical Drive (Boot Sector)
  3. Jaclaz - wow - very informative. Thank you! Your description confirmed my guess that the D partition was only the Dell Utility partition, and so just now I was successful in removing the D drive letter and rebooting. It no longer shows up in Explorer - good - just like before the clone. (That Dell utility partition still shows in Disk Management, but now (again) without a drive letter.) As to the two mystery partitions that you saw - they are a historical artifact. Originally, the Momentus XT drive was purchased as a replacement drive for my wife's Dell Win xp laptop. But that laptop had a meltdown shortly afterwards, and she moved to Apple, never to return to MS. I saved that Momentus XT drive, which had her laptop C; and Dell utility partitions on it. A little bit later, when I needed to replace the original hard drive in my Dell Optiplex 755 (on which I am writing now), I used that Momentus XT. But the first thing I did was to hide those two existing partitions very thoroughly, rather than delete them, just in case she needed a missing file. I moved my XP Dell Optilex onto the remainder of that Momentus XT, where it functioned in my Dell Optiplex 755 for a few years. Recently, the Momentus XT seemed to hiccup, causing network interruptions and re-downloads of my current aol email. So. yesterday, I finally cloned it to a plain vanilla WD hard drive but keeping those deeply hidden old partitions in place (also on yesterday's clone), Here we are. So far so good. Thanks also for pointing me to that tool HDHacker. I did not go to the trouble of saving the MBR info from the now-removed Momentus XT but did just now save the info from my new WD. In case you're interested, here is the link to my two dat files - one from the logical drive and one from the physical drive: https://my.pcloud.com/publink/show?code=VZLjHJkZeUTX4PBaO4urWUsVN9pDfYOBfvN7 Of these two dat files. When I "Compare with loaded", the dat from "Logical Drive (Boot Sector)" is the same as loaded, and the dat from "Physical Drive (MBR)" has many differences from as loaded. Don't know what that means. What do you think?
  4. Actually, the more I think about the files in this D: partition, the less sure I am that it is boot-up (MBR). Maybe it's just the Dell utility partition? I can't tell. But it didn't have a drive letter before. What does your boot-up - MBR partition look like?
  5. Nice to see there's still life in this XP part of the forum. Using Macrium Reflect Free version 7.2 in a bootable USB stick, I finally cloned my XP drive from my Momentus XT hybrid drive that seemed to stutter (the source) to a plain vanilla WD hard drive.(the destination). This was a direct clone - I had both drives inside my machine (an Optiplex 755 Desktop with 4GB RAM) when I ran the clone. Immediately after the clone, I shut down, removed the Momentus XT, moved the WD to the SATA cables that used to go to the Momentus XT, rebooted using the Macrium USB stick into the Macrium PE environment and used the Macrium to "Fix Windows Boot Problem". (I did this because a prior effort to clone the Momentus XT onto this WD failed with BSOD screens when I tried to boot up the WD.) Well, with one exception, the clone seems to be working fine 12 hours later. Still keeping an eye on it. Here's the issue -- and, remember, I now have only the clone WD hard drive in the machine. In Explorer, in addition to the C:\ drive (good), I am also seeing a D:\ drive that seems to be the bootup (MBR?) partition. I would NOT normally expect it to have a drive letter or be visible in Explorer. If it's visible, I might screw it up someday. What should I do? Just eliminate its drive letter in Disk Management? Should I go into Safe Mode first to do that? Will the machine still find it to re-boot next time? If the machine can't find it and won't re-boot next time, what would I be able to do to re-assign it as D:\ and so at least be able to re-boot? By the way, I'm a lawyer, not a tech person, and I don't know what I'm talking about. (We lawyers never do - we just make it up as we go along, which is why you can't understand us. And then we send you a bill) I don't know what MBR means. I can tie my shoelaces and boil water, but that's about it. I don't seem to be able to insert any graphics here, but here is a link to a png of a screenshot of what this D drive looks like. https://my.pcloud.com/publink/show?code=XZ2dJJkZwAFz8nML7LkBhJcYaUFWTVvhGkw7 Looks like the bootup - MBR partition, yes? Now, here's a link that shows what my Disk Management looks like: https://my.pcloud.com/publink/show?code=XZltJJkZXktXYt3NRQHOEz3yFnTGaJaiYDLV (Those two partitions on the left surrounded by a green border are deeply hidden partitions that were on the Momentus XT when I removed it from my wife's laptop ages ago. I wanted to use the Momentus XT in my XP machine but also wanted to preserve those partitions. They are not active and the XP machine has never noticed them (good). The two partitions that count are the two on the right. I can't do a screenshot, but if I right-click the D: partition, I see an option to "Mark partition as active", which I suppose means it is not active yet. If I right-click the C: partition, that option is greyed out, which I suppose means the C: partition is already active, which makes sense.) So - should I just use Disk Management to remove the D: drive letter from that partition? But please see my questions 2 and 3 above. Thanks.
  6. Here's the report in Macrium Reflect of yesterday's clone operation. See anything interesting?
  7. SEE EDIT AT END Vistaboy and jaclaz -- thank you both. I might have to re-clone and try again, but I'm fairly sure the clone's partitions were the same "active" or not as the original. Also, I did not have both drives plugged in at the same time with normal Windows running. For this clone, the Macrium Reflect is on a bootable USB stick in Win PE, and so normal Windows XP was not running while the clone was made and verified. Before starting the machine into the bootable USB Macrium, I powered down, removed the CD-DVD drive, attached the "new" WD HDD to the CD-DVD drive's SATA cables and then booted into the USB stick. The PE environment Macrium found both disks, the original with its partitions and the new one blank, so it was easy to run the clone. After the Verify, I shut off the PC completely, removed the original Maxtor Hybrid HDD+SSD and put the new clone (on the WD HDD) in its place, using the original's SATA cables, and put the CD-DVD drive back. Then booted up and got the BSODs. (However, similar steps worked when I cloned HDDs in my separate dual-booting Win 7+10 machine, using a similar USB stick, that one with Macrium 64-bit.) One thing occurs - again inspired by jaclaz's info: In the Macrium 7 clone advanced settings, there is an option for Enable SSD Trim, whose default was on. I left it on. Now, my original HD+SSD is a Maxtor MomentusXT (a hybrid HD+SSD), and I do NOT know whether it was aligned with Trim because (I recall from a long time ago) this model Hybrid maybe did NOT require 4K alignment. So maybe, for the clone onto a non-hybrid WD HDD, I should have turned Enable SSD Trim off? FYI - I never looked at that registry key before. It has 47 Reg Binary lines! \DosDevices\C: has the value 80 61 02 00 00 00 30 0a 14 00 00 00 A few other of those 47 lines have the same value. But I don't want to touch this key. Anyway, further thoughts? EDIT - Right now, on my original Maxtor MomentusXT (hybrid HD+SSD) disk running XP, the "Cluster Size" is 4 KB. So maybe my surmise above is incorrect.
  8. Just spent most of the day cloning my old hard drive in my XP machine to a newer although slightly used one, but when I boot from the "new" one, I get BSODs. So I put the old one back in and can boot OK. The old one (currently running) is a 488GB Seagate ST95005620AS, which is also known as a Maxtor Hybrid HDD+SSD. The "new" one is a classic 500GB WD5000AAKX, which had worked fine in another machine. Before I did the clone, I wiped the WD and formatted it for NTFS. I did the clone with Macrium Reflect 7.2 running on a bootable USB stick, and I had the clone do a "Verify". The WD clone would start booting and after the black XP screen with a progress bar would trigger a BSOD. When I retried in Safe Mode, I saw the drivers load (the vertical list of drivers in white letters against a black background) so I know the machine was able to read the drivers off the WD clone, But again a BSOD. Rebooting into "Last known good configuration" did not help, and I also could not boot into Safe Mode Command Prompt. I was too dumb to mark down the BSOD stop code. I also F12 booted into BIOS and turned off Keyboard Errors - no help. Any fast ideas? Thanks.
  9. jaclaz - your info prompted the fix! I didn't actually follow what you wrote, but your detail above made me realize that possibly my OTHER USB external hard drives were grabbing my PC's attention during F12 bootup ahead of the USB stick. The F12 menu only mentions USB device once, generically, not a list of my three USB items. Of course, my two external USB hard drives are NOT bootable - they are just extra storage. So the PC was looking to one of them first and giving up before trying the stick. I unplugged those two USB cables from the back of the machine, and now the machine boots from the USB stick!!! Macrium Reflect loads up and is ready to go. (Haven't run it yet - more work before I do.) [Before thinking of this, I also went into Device Manager, marked down the actual driver files (sys and dll) for the various USB items in Device Manager and then copied those exact sys and dll files onto the stick in about twelve places. Probably irrelevant, but hasn't hurt.] Molto grazie! Sorry for the weather in Europe!
  10. jaclaz - thanks and greetings. When I reboot the XP machine and hit F12 for the boot menu (white letters on black background), and then select USB Device, I get only error messages - F1 to retry, F2 reboot and F5 diagnostics. No BSODs. But if I put the same stick in the 7 machine and hit F12, when I select USB Device the machine boots into the Macrium PE environment. Earlier, after the initial failures, I partitioned the stick, cleared it, followed the Macrium instruction to format it with NTFS -- all no help. The final was to redo it as FAT32, back to the starting point. There is a chance that the stick doesn't have the right USB drivers in the right place, but I'm not sure about that.
  11. cdob - thanks, but that article is 1,000% beyond my abilities. I had hoped Macrium's rescue media creation tools would just do it, but I guess not.
  12. Mikey - it says "3.0 ... compatible with USB 2.0". And when I first made it on my XP machine (which has only 2.0), it showed the files I had copied into it but just wouldn't boot. I also tried re-formatting it as FAT and exFAT and NTSF, and on the last occasion first turned the Macrium Reflect into an .iso and burned it onto the USB stick using Rufus. Nothing has worked so far to make it boot,
  13. I am unable to get my XP machine (Dell Optiplex 755) to boot from a USB stick. I have put Macrium Reflect Free (Rescue Media) on the USB stick, but the XP machine just won't boot from it. The same stick will boot my Win 7 machine and run Macrium reflect in its PE 3.1 environment on that newer machine. Is there a way to get my XP machine to do the same? Thanks.
  14. Thanks, Mathwiz! And don't you and I feel lucky that, unlike poor Europe, we have air conditioning!
  15. Hey - was driving by and thought I'd stop in for a cup of coffee (actually to use the bathroom). Probably some of the preceding posts answer my question, but I'm in the bathroom reading a C. J. Cherryh sci-fi novel, so please let me know which recent surprise updates deal with https://support.microsoft.com/en-us/help/4500705/customer-guidance-for-cve-2019-0708 and https://www.askwoody.com/forums/topic/bluekeep-is-almost-here-get-your-xp-win7-systems-patched, and are they just there in Windows Update Catalog and do you like them? Besides that, did I miss anything else the last few weeks? All you Europeans enjoying the weather? Thanks.
×
×
  • Create New...