Re: Tutorial creating & using Hirens Boot CD & MemTest86 diagnostic stress testing tools for USB boot to Windows 10 PE & WinXPmini on BIOS & UEFI
Arlen Holder <[email protected]>
| Newsgroups | alt.comp.microsoft.windows,alt.comp.os.windows-10,microsoft.public.windowsxp.general,alt.comp.freeware,comp.sys.hp.hardware,alt.comp.hardware |
|---|---|
| Organization | Mixmin |
| Message-ID | <[email protected]> |
On Sat, 26 Sep 2020 04:56:47 -0700, Mike Easter wrote: > Arlen Holder wrote: >> In summary, if you have an XP machine off the net, you might consider >> booting to the Hirens XP which seems to work as well or better than the >> original XP did. > > That isn't the way I would 'do that' -- where 'that' is breathing some > life into some old hardware which is lying around fallow. Hi Mike, Yes. But. In reality, I was needing a sneaker net because I scanned in a document with my ancient Dell Inspiron B130 laptop connected, via USB, to my almost as ancient HP laserjet 3200m which I only use as a scanner. I needed to bring the scan to another machine, so I grabbed the recently created winXP hiren's boot USB, and then figured, what the heck. I may as well see if it boots on the ancient Dell laptop (it's so old it has only 1/2GB of memory, and only a 149GB HDD - it's got to be more than 15 years old - and it's still (kind of sort of) kicking! It booted, and it's still running virus scans as we speak. > The biggest advantage of the linux over the OEM XP are that it runs a > modern browser. This is a good point of the modern tools for an old-as-hell laptop. o And, another key advantage is you can put it back on the network. As long as it works with the HP LJ 3200m scanner, I'm fine with Linux. > Since your machine has 2G ram, it has even more linux options than my 1G > machine; likely the 'bottleneck' restricting choices would be what its > old graphics are, which we don't know at this point. Actually, it has only 1/2 GB of RAM. o It's a $500 Dell Inspiron B130. -- BTW, I was able to create, on Win10, crash logs, which I was writing up the analysis in deep detail last night, when that BSOD Win10 machine crashed again, and again, and again, and wouldn't boot until this morning. Sigh. Details to follow in the BSOD thread.