Windows 10 is running slow -- Fixed

Thanks Kevinpg. I certainly don't mean to offend you or anyone else. I just remember that from my college days. It was mentioned by the class professor. Thank you for the link, very interesting. Those costs are amazing. Hard to believe how far we have come.
 
OK, still off topic ... but I've been fascinated by core memory since 1965, when I was first exposed to a computer (IBM 7094) and learned to program in Fortran. Over the years, I've heard various stories about manufacturers hiring weavers and other types of persnickerty ladies, from Japan and various other places, to string the beads. Then in the late '60s I heard some wonderful news about NCR's "rod" memory. Instead of hand threading wires through donuts, NCR devised a way to wrap wires around rods. They used a magnetic field to align the rods perpendicular to a pre-drilled board. Then somehow fastened them in place. Then used machines to wrap the wires around them. No more hand labor, and a huge cost savings! Unfortunately, solid state memory came along shortly thereafter, and magnetic memory became a thing of the past.

1968 NCR ad:
NCR 1968.jpg

For those who're not familiar with this dinosaur-level technology, I'll give a quick explanation of how it worked:

Each core (bit) in a grid typically had three wires threaded through the donut hole - X and Y wires, unique to each row (something like the byte or word address) and column (bit position in the byte or word) of the plane, plus a sense wire, which would typically be run through a large number of rows and/or columns.

To write a 1 or 0 (represented in the core by the direction of magnetization), one X wire and one Y wire would each be supplied with half the current needed to magnetize the core. Only the selected core would be set, because magnetic hysteresis prevented anything less than full current from affecting any of the other cores. The direction of the currents would determine the direction in which the core was magnetized.

To read a bit, the memory module would try to set (write) the selected core to the 0 state. The sense wire would detect whether the state was thereby changed or unchanged. If it was changed, the memory module would go through a second cycle and restore the original (1) state. This was known as a "destructive read".

Bottom line- you could only access one bit at a time. And the cycle time in the early days was 6 microseconds. As with everything else, it did go down ... to about 0.6 microseconds in the mid '70s [info from Wikipedia article]. To put this in perspective, 0.6 milliseconds = 1.67 MHZ. Compare that to the GHZ speed of your current hardware!

The initial cost of core memory was about $1 per bit. It fell to 1¢ per bit by 1974, when solid state memory took over.

Further refinements - If you look at the core planes photos I posted earlier, you'll see that there are several grids of cores. These grids were organized by the designer to optimize how the memory would be used. "For instance, a machine might use 32 grids of core with a single bit of the 32-bit word in each one, and the controller could access the entire 32-bit word in a single read/write cycle." [Wikipedia article]

Here are links to articles that might be of interest:
https://en.wikipedia.org/wiki/Magnetic-core_memory
https://ub.fnwi.uva.nl/computermuseum/CoreMemory.html
https://en.wikipedia.org/wiki/Rod_memory
http://www.computerhistory.org/revolution/memory-storage/8/253
https://nationalmaglab.org/educatio...lay/interactive/magnetic-core-memory-tutorial
http://www.chipsetc.com/rod-memory.html
 
DEATH TO WINBLOWS!

Except for games, it is best for games...

I have a monster of a computer...
Watercooled i7 4790k
32gb ddr3
Two watercooled gtx 1080 titans
12TB in a 9TB RAID 5 setup
5TB in SSDs

And I have a 200$ linux box for cnc, cad and cam...

The crazy thing is that my monster doesn't do much better than the $200 linux box at what the Linux box was designed for.

My windows machine even has a Linux partition because for 3d rendering and animation I get about 60% more preformance, which depending can mean days of render time...
 
Hey.... thanks for the info... I'm still running XP and i will until I cant.
You'r info helped me with a program that I could not get rid of. It
was bothering me for about a year. I could not even find it in redg-edit.
Skimming through services.msc found it for me. I disabled it. thanks again.

Talking about old computers I started out with a Vic-20...
 
If I could get Win 7 to run on my new machines, I'd use it in a heartbeat. The latest PC standards weren't thought of during Win 7 days. My Win 10 (ugh.) runs on 4GB memory, but someday I'll upgrade it.
 
If I could get Win 7 to run on my new machines, I'd use it in a heartbeat. The latest PC standards weren't thought of during Win 7 days. My Win 10 (ugh.) runs on 4GB memory, but someday I'll upgrade it.

I'm running AutoCAD 2000 in an XP virtual machine using VirtualBox on a Windows 10 laptop. VirtualBox is free from Oracle.
https://www.virtualbox.org/wiki/Downloads
There are other popular options.

You can run nearly any OS you want in a virtual machine regardless of what the OS of the host computer is. It's not that hard to set up, if you can do a Windows installation from disk, you're advanced enough. I've installed it for several of my customers so they can continue to use old software. The other big advantage is that the whole "computer" is contained in one file which is easily backed-up or transferred to another computer when you upgrade. Just imagine getting a new computer and having it look, feel and run exactly like the old one without having to reinstall your programs and data.
 
You can run nearly any OS you want in a virtual machine regardless of what the OS of the host computer is.

With only 4GB of memory, a VM won't run well under Win 10. If I go to 16GB, your suggestion makes sense. I don't hate Win 10 -per se- I hate its constant updates and slow performance, which will stay the same if I use a VM under it. I have taken care of the update problem. Performance can't be helped much, even with lots of memory: Win 10 is a CPU hog.
 
Thanks, Jim, That's the solution to the problem I've been having.
 
I run windows 10 Pro and have very few issues. I also have linux and mostly use it to play with, I run MVS 3.8 on top of it. Of course I was in IT from 1972-2015
 
Stonebriar, I suspect you have more than 4Gb of memory...

I cannot allow updates because of a history of M$ destroying my firewalls and VPN software (5 times until I stopped all updates). I use about 200 apps, some of which break on each update. I protect my computer in other ways than patching the OS, and I've never been infected. BTW I worked in IT for one of the big 5 consulting firms for 15 years, 35 years as a consultant total. (So I'm not a nube)...
 
Back
Top