Remember that 8088 or XT based PC’s ran their ISA bus at 4.77mhz, AT ran at 6mhz, and 386 and beyond ran ISA at 8mhz (though many later ISA systems ran them at 10mhz since ISA is very forgiving and the higher clock speed gave better speeds). This means you may find old 8-bit or AT-based ISA cards won’t work in AT or 386/486 systems since the ISA bus runs too fast.
If your BIOS allows it, you may be able slow down the ISA bus speeds and that might help old cards work.
Microsoft has recently release DOS 4.0 as MIT licensed OpenSource.
Dave’s Garage does a walkthrough of the history, sets up a dev environment (masm and C 5.1 compiler), builds the source, then bonus points for writing it to an actual 5.25″ floppy using a greaseweazle. He then boots it off an actual IBM XT.
Recently I acquired some old pc hardware and put together a retro 486-DX pc. To that end, I needed to create a DOS boot disk for this old system. That meant I needed to write a 1.2mb DOS boot disk.
I floundered around with greaseweezle’s command line but this guide from Tech Tangents really helped out. There’s clearly a lot more I need to learn, but this got me a bootable 5.25″ 1.2mb floppy disk. I was able to test it on 2 different drives, and both worked. So, that’s pretty sweet!
Greaseweezle command line samples
How to write DOS 6.22 image to a 5.25″ 1.2m floppy drive attached to the ribbon cable right before the cable twist:
gw write --drive b --format ibm.1200 Dos6.22-5.25.img
To write a DOS 3.30 image to a 5.25″ 360k floppy drive attached to the ribbon cable right before the twist:
gw write --drive b --format ibm.360 DOS330-360k.img
Carnegie Mellon researchers have developed a real-time human tele-operation system. Using a simple camera, it is able to read the actions of a human person and then translate that into real-time full-body control of a robot.
Individuals can now seamlessly teleoperate full-sized humanoids to execute a myriad of actions. According to researchers, they can perform simple tasks like picking and placing objects to dynamic movements like walking, kicking, and even boxing.
There’s lots of possibilities for this kind of remotely operated humanoid robotic system. Remotely controlled humanoid robots could save countless lives operating in dangerous environments.
They could be used to go in and shut down equipment after dangerous chemical or industrial accidents. Search dangerous buildings for survivors after earthquakes. They could perform dangerous police or urban warfare operations without loss of life. Stop terrorist by defusing bombs. Another such place would be effecting repairs, shutdowns, and cleanup in highly radiated areas like Chernobyl, Fukushima, or when there are nuclear accidents. In the future, we may never need the horrors of Chernobyl’s biorobots to deal with such disasters.
I wrote awhile back on how to crash Linux/cause a Linux kernel panic in order to test how your program can handle a crash – but can you cause a Windows blue-screen programmatically?
Methods you can use to cause a Windows Blue-screen:
Windows allows you to configure a specific keyboard combination to cause a crash. You set some registry keys and then can crash a system by holding right CTRL then pressing scroll lock key twice. You can also customize the key sequence via registering custom keyboard scan codes. If you have a kernel debugger attached it will trigger the kernel debugger after the crash dump is written.
The best way to trigger an artificial kernel crash is to use NotMyFault, which is part of the Microsoft Windows SysInternals tools.
nVidia’s CPU stacks up respectably against the AMD Threadripper 7980X
More eyes are nVidia’s GH200 Grace Superchip. The GH200 Superchip is the combination of a Grace CPU and a Hopper-based H200 GPU. While the results aren’t definitive, they should raise eyebrows.
In 39 individual Linux-based benchmark tests, Grace (the CPU side) beat the AMD Threadripper 7980X in 17 tests and the 7995WX in 15. It even stacks up well against Intel Sapphire Rapids.
Sapphire Rapids and Threadripper enjoy many advantages. Far more apps are optimized for x86 than for Arm. Threadripper has much more aggressive clock speeds than the efficiency-focused Grace chip and far more L3 cache (7980X has more than double, and the 7995WX more than triple).
But raw performance may not be the only consideration. There is speculation that Grace Hopper is more energy efficient – but there is no real data on TDP outside the whole package requirement of 500w. Also, for tasks that are more GPU bound than CPU bound, the combination may provide higher effective processing power than a faster CPU paired with a discrete GPU. Time will tell.
It shows that nVidia’s Grace entry is not to be ignored. Paired with the Hopper GPUs, it might offer a very viable alternative to x86 stacks – if your software can run on Arm.
ZZAZZGlitch shows us how in his video. Wow. He even made the source code is available on his personal site, labeled “gbacrashsound_dumper.zip”. It still took a LOT of hacking and manual fix-ups; but he got a bootable game in the end.
Massive in the 90’s, Demoscenes are not dead. Revision 2024 demo party just took place March 29th to April 1st in Saarbrücken Germany.
There was music, seminars, videos, livestreams, a 5k run, and of course – amazing code demos. This included some competing 256-byte demos here. One of the best was a post-apocalyptic black-and-white city created with just 256 bytes of Gopher code running on DOS.