And I have to say, it’s pretty impressive! Previous flies on my system, having owned a cube, I can say that the 68030 on this is WAY faster. And I’ve always read about 0.8, and kind of figured it was basically lost to the winds of time. It’s really cool to see it boot up! And the emulated disks are so much faster than the magnetic optical drives of the day.
It’s amazing to think that in 1988, the current world of iThings had just started.
Ok, I’m getting nowhere quick on the sound thing so I’ll release what I have now. Thanks to the instructions here, I’ve setup a package which can be easily installed on NeXTSTEP.
Simple, right? Just download the package, and you should be able to install it with no issues. I’ve built it for all the CPU types that NeXTSTEP supported so let me know if you have any luck…
Also I’m going to leave the quake server running on my server, the only issue is that the hostname is too long for Quake to deal with, so you’ll have to type in the ip address (184.108.40.206). Also you’ll have to launch this from the command line… 😐
If anyone has any hints on audio streams on NeXTSTEP drop me a line…..
I took the unix timer code, and got that working (not surprising, NeXTSTEP still is 4.3 BSD at heart), and I fixed enough of the key bindings so it’s getting playable. In addition I went back through the WinQuake source and pulled out the BSD networking and that works great. There was a sound driver in there for the next, but it lacks the output functions…. So it would seem that’s the last thing to hack through for a more ‘complete’ Quake experience.. well that & the mouse.
I’ll probably dig around to find out how to make one of those nifty NeXT packages, and release a test version since it’s playable ‘enough’…
At least the video is kind of working… Right now I’m still using the cannibalized stuff from the UAE project’s port to NeXTSTEP. This is what I used for Frontier, although I’d like to think I’m getting a slightly better handle on it. Right now I just have to figure out why my keyDown & keyUP handlers are not working…. And implement the timer so it doesn’t run at warp speed. With the timer in place it should be able to do network play.
I suspect this would be FAR too slow to play on the m68k,Sparc or HPPA hardware but then who knows… My monitor for my m68k is broken so I can’t run it to find out…
This runs VERY fast on Qemu 0.90 I may have to rewire some stuff to run in on my whitebox, but I have a feeling I’m going to have to re-install… I forget where I left off on my NeXTSTEP setup on the old P4.
Anyways that’s what I have for the last few hours….
Well I couldn’t resist. Currently there is no keyboard input, but after hacking the ObjectiveC from UAE, I was able to get GLFrontier to compile and run it’s intoduction under NeXTSTEP 3.3 on VirtualBOX…
I guess I’ll have to break down and order some new hard disks, and a PCI video card to rebuild me a whitebox.
This moves the soundblaster to IRQ 7, and incorporates a bus fix & busmouse additon. Remember to remove the parallel port for this to work correctly. Tested with NeXTSTEP 3.3
Why all the patches, you may ask? Well for some reason NeXTSTEP is unable to correctly drive the mouse in Qemu. Nobody has tracked it down, but I suspect it’s some wierd issue with the BUS… Anyways I found this busmouse patch ages ago, and I’ve just been finagaling it for ages so that it will keep on working. I know that there are a hand full of enthusists left, but I figure that for all interested they would appreciate this.