more win10 fuckings

[RJARRRPCGP]

Re: more win10 fuckings

Extended memory is himem.sys, not EMM386!

[Curious.George]

Re: more win10 fuckings

^ Its EMM386 thats fucking off....

Turn it off. I think Windows will still load but will be cramped for memory.

Or, use something like 386MAX.

[goontron]

Re: more win10 fuckings

^ Huh. I didn't even think about that. QEMM v9 should work damn fine...

[stj]

Re: more win10 fuckings

been decades, but wasnt there a replacement for that?
something like qemm386?

and then you have freedos - that's full 32bit and handles modern hardware.

[goontron]

Re: more win10 fuckings

^ Its EMM386 thats fucking off....

[Curious.George]

Re: more win10 fuckings

Not only, but hardware is getting TOO fast for legacy software. I can't for the life of me get my Windows 3.11 VM to boot on my new laptop. The fucking Xeon CPU is too damn fast.

Likely a sign of a race, somewhere, in the code. Hard to test for so it has to be avoided at the design stage.

My biggest lament is losing Brief. Too many timing loops that now run so fast you can't type without filling the screen with that ONE character!

[goontron]

Re: more win10 fuckings

I often have to run legacy DOS programs in a DOS box or VM. It's insane to see how lightning fast they are -- without having been penalized by the bloat that accompanies applications and the OS!

Not only, but hardware is getting TOO fast for legacy software. I can't for the life of me get my Windows 3.11 VM to boot on my new laptop. The fucking Xeon CPU is too damn fast.

[Curious.George]

Re: more win10 fuckings

I remember downloading SP6 for Win NT4 from a 56k connection. IIRC, a whopping ~35mb service pack.....

NetBSD 0.8 (1993) was about 12MB (compressed) in groups of 240KB files (5 of them on a 1.2M floppy; 6 on a 1.4MB floppy!). The sources (almost essential if you were running something that new) were another ~28MB. At 19.2K it took FOREVER!

How big would a W10 SP be? Add a couple zeros to that 35.....sad.

The saddest part is when you look and ask yourself, "What can I do, now, that I really couldn't do, before?" And, "How much of that was made possible by the OS vs. just hardware advances over the years?"

I often have to run legacy DOS programs in a DOS box or VM. It's insane to see how lightning fast they are -- without having been penalized by the bloat that accompanies applications and the OS!

[Topcat]

Re: more win10 fuckings

I remember downloading SP6 for Win NT4 from a 56k connection. IIRC, a whopping ~35mb service pack.....

How big would a W10 SP be? Add a couple zeros to that 35.....sad.

[Curious.George]

Re: more win10 fuckings

IIRC, that's when I downloaded Ubuntu on 56K, LOL

I DL'd NetBSD in '93 over a 19.2K PEP. Onto 5" floppies!

[RJARRRPCGP]

Re: more win10 fuckings

July of 2005.

IIRC, that's when I downloaded Ubuntu on 56K, LOL

[Curious.George]

Re: more win10 fuckings

+1000!
i know someone right now who wrote stuff to dvd-r years ago and now finds half of them unreadable.

Did you ask him HOW he wrote them, what sort of media he used, and how he's stored them?

I just pulled the top (recorded) DVD-R off a spindle and checked it (I have the hashes for every file on every medium STORED in a database so I can do this -- instead of just relying on "can I read the disk"). The medium was written in July of 2005.

i tell folks to properly back their important stuff up properly or just delete it now to save worrying about WHEN a disaster occurs!

And how often do you tell them to check those backups? Verify that the media still works, is still readable and that NONE of the contents have been corrupted (or "disappeared")?

I have a database that tracks the structure of every offline storage medium (path, filename). Additionally, certain metadata like size and hash. For each, it tells me the last time the file's contents (via its hash) have been verified.

Whenever I mount one of those media (to retrieve something from "cold storage"), my software takes note of the media ID and verifies the signatures of its contents, beginning with the file least recently verified. A successful verification gets recorded in the database as "date of most recent scan". A failed verify is reported to me (via email) along with the device/path/file of an identical copy of the failed file (I have to take manual steps to restore it as that means mounting another drive, etc.)

Daily, a cron(1) job scans the database to determine which files (if any) need to be verified (based on how long since their last check). I am prodded by an email to "please mount drive #74" -- once mounted, the software will do the rest.

Even my optical media sits in this database. So, I end up with a record of when (and if!) each have been checked, most recently.

But, of course, YOU already do this, right? (even if you have to do it all MANUALLY with a crib sheet of hashes scribbled down from some previous scan)

[Curious.George]

Re: more win10 fuckings

super easy to back that up.
no excuse for not doing it.
if its not a bad windows update it will be a failed drive.
something WILL bite you in the ass someday.

No, nothing will "bite me in the ass" cuz I have several off-line copies of everything on ALL of my workstations/servers.

And, I'm not stupid enough to run W10 *or* have any of my systems exploitable (intentionally or not) by "remote actors" (MS/malware).

There's no reason for an OS update to touch anything other than "system files". And, no reason for a an application update to touch any files other than the files that implement that application.

When you bring your car in for service, you don't expect the dealer to have emptied EVERYTHING from your glovebox -- in the name of cleaning up all that "clutter" -- with the exception of the things you've previously told him should remain ("I don't recall anyone telling me that! Time to find a new dealer!!")

[kc8adu]

Re: more win10 fuckings

super easy to back that up.
no excuse for not doing it.
if its not a bad windows update it will be a failed drive.
something WILL bite you in the ass someday.

It was at "C:/Users/rober/Documents/".

[kc8adu]

Re: more win10 fuckings

+1000!
i know someone right now who wrote stuff to dvd-r years ago and now finds half of them unreadable.
thats hundreds of disks.
fortunately its just a porn collection.
i only use them for short term portability.
i tell folks to properly back their important stuff up properly or just delete it now to save worrying about WHEN a disaster occurs!

Who would ever be that trusting of writable optical media?! I've had too many of even the 'high end' discs go bad. I backup to multiple external HDD's and store them in several secure off-site locations.

[Curious.George]

Re: more win10 fuckings

Who would ever be that trusting of writable optical media?! I've had too many of even the 'high end' discs go bad. I backup to multiple external HDD's and store them in several secure off-site locations.

I didn't say they were *copies* of the original files but, rather, *THE* original files. "Factory-pressed" optical media has, IMO, a pretty reliable long term reliability.

[OTOH, I've actually had very good results with OTS consumer optical media. But, I store it cool & dark, record at the slowest speed possible, etc.]

My point was that it is not practical to drag out a couple of spindles of original discs in the hope of finding a "good musical score" or "suitable background imagery" when producing a multimedia presentation. You want that available to the application that already knows how to parse it's particular format so you can browse the potential candidates instead of relying on a list of cryptic filenames to evoke some sense of what the actual content is like!

Even accessing spinning rust archives of the entire sets of media doesn't give you access to the INSTALLED versions of the files -- which often include metadata that can't be gleaned from the filename, itself.

CllipArt is similar. Though there are tools that you can use to build catalogs that you can browse as conveniently as the original media -- assuming the original media is in a "standard format" and not something proprietary (to a custom browser published by the clipart vendor).

[Topcat]

Re: more win10 fuckings

...while I can have 150+DVDs with the original files on them

Who would ever be that trusting of writable optical media?! I've had too many of even the 'high end' discs go bad. I backup to multiple external HDD's and store them in several secure off-site locations.

[Curious.George]

Re: more win10 fuckings

What a moron...

Who has 220GiB files in his Windows Folders??
You put that elsewhere...

It was at "C:/Users/rober/Documents/". Where do you suggest he put it? Note many systems have a single physical disk, nowadays. Each of my Windows workstations has 4T of spinning rust -- the OS itself being an insignificant portion of that.

I have several HUGE libraries (for producing multimedia, doing 3D CAD, Schematic capture/PCB layout, etc.). The software that uses these libraries expects it to reside on the same system and, often, in a FIXED location on that system! So, while I can have 150+DVDs with the original files on them, those all need to be decompressed and "installed" (not just "copied") on the machine to be of any use, to me. (Kinda hard to "browse" audio/video content when it's offline!)

[stj]

Re: more win10 fuckings

he did back it up, just not very often.

i'm more interested in the fact that the update deletes files in a folder tree it has no reason to touch.
UNLESS they are flagged as mirrored to m$ servers (azure network?)

it sounds like a move to coerce people to use the m$ mirroring service - for their own safety.
(because it's always for your own safety, or for the children - right out of the government playbook!!!)

[Stefan Payne]

Re: more win10 fuckings

dont delay - upgrade to cloud(one drive) today! >>>
i'm damned sure this was no accident!
https://www.zdnet.com/article/window...river-warning/

What a moron...

Who has 220GiB files in his Windows Folders??
You put that elsewhere...
And 220GB is rather small so you could back that up easily...