scruffyherder

when testing native builds I was using a Xeon E5v2.

why bother with anything slow as a p3?

DLL's were the most involved part of the port.

I've no idea why so many people struggle with this.

I have to admit, that I was surprised when they all came back good! We already had the SDK on 3 1/2" disks, so we could compare the contents. Oddly enough all the executables, libraries and headders are a match but the helpfiles have a different CRC, despite being the same timestamp, and size.

I've installed it on 86box, and then converted the boot disk from 5 1/2" to 3 1/2" inch so I could install it on VMware and my IBM PS/2 model 80. That's another surprise I thought for sure the PS/2 drivers would be missing from the 5 1/4" disk version, but they were there!

On VMware the AT version of the PS/2 mouse driver locks the system up, but I copied the one from 6.123 and it works fine. Although there is no MS-DOS sessions working.

Also as a follow up on my 'dont waste money on a math co-processor' if you have the 'passthrough math' on 86box the dos sessions misbehave big time. Using the softfloat option for more accuate floats results in working MS-DOS. - Turns out OS/2 betas really did rely on a FPU!

It's the full OS + SDK and the networking bits & kernel debugger as well!

It’s really cool to run dec alpha binaries on x86!

Pharlap 386 is mentioned on Links386, although its flies on by, and special->about

Pharlap's TNT was way more exciting to be honest.

I'm still trying to find the first early extenders though from 1987/88 no leads though.

Wow that's pretty cool! I first found out I had some virus when I was hex editing my boot/root floppy disks for Linux back in 92? I'd just compiled a kernel and forgot to set the root to the hard disk, swapped disks around and found some bootsector thing that I can't remember at the time. It was initially mystifying how it read okay in DOS, as the virus could hide, but on Linux is where it was laid bare.

Pretty cool how you made such a massive leap! Talk about making lemonade!

Nah, it was wp-mail-smtp. It completely crashed out on me.

> PHP Fatal error: Uncaught TypeError: ActionScheduler_Action::set_schedule(): Argument #1 ($schedule) must be of type ActionScheduler_Schedule, ActionScheduler_NullSchedule given

I've been able to take 2 million hits a day, so it's not that!

I'm hoping to pull it out of storage and give it an update. There is newer processors, although they are still about the same price, and I'm not sure it's all that worth it.