NeXT Computers

[stevebez]

I don't know if it matters, but the "regular" version of Q runs fine, except for NS/OS.

[stevebez]

[helf]

"Simple DirectMedia Layer". It's a crossplatform api/toolkit a lot of games and stuff use.
_________________
*INACTIVE*

[bkmoore]

I know this is an old thread. I got the version of Q working from kb7sqi. It was compiled with dependencies. You need to install MacPorts - libpcap in the /opt/local/lib directory first.

Brian

[andreas_g]

Hello Brian!

could you provide us with detailed instructions on how to install libpcap?
i just tried it myself, but failed. i do not have experience in such things.

on which system are you running q? my system: iMac G5 with 10.5

it would be really great, if you shared your knowledge of how to get this custom version of Q running with us.

thanks a lot!

Andreas

[bkmoore]

Andreas,

Schöne Grüsse aus Hawaii.

The version of LIBPCAP that is installed by MacPorts has a different name than the version that Q is looking for. What you need to do is create a symbolic link to LIBPCAP so that Q can find it.

cd /opt/local/lib

sudo ln -s libpcap.a.dylib libpcap.dylib

That should do it. If you still have issues, use the preferences in Q to display output to the Console. Then use the Console to track down the error.

I hope this helps,

Brian Moore

[andreas_g]

brian, thanks a lot for this information!
you lead me into the right direction, but the dynamic link wasn't 100% correct.

i found out the requested filename via console. just type into terminal:

sudo ln -s libpcap.a.dylib libpcap.0.dylib

now the installation process of nextstep 3.3 is running, hope everything goes well!

[andreas_g]

Update:

NeXTSTEP 3.3 now works properly. I have installed the video driver from "http://www.nextcomputers.org/NeXTfiles/Software/NEXTSTEP/Drivers/nextstep_3.3/released/CL_GD5434.pkg.compressed". (download file, make an mac os standard disk, 1,4 MB with disk utility, unpack file in os x, copy package into image file, load image as cd in nextstep, then install package)

configure.app recognizes the driver, i chose 2 MB mode. the only mode that seems to work is 1024 x 768, 75 Hz, 16 bit color depth (which is great)

next i am going to try setup networking and sound!
if anyone has an idea how to set up internet an network, please post the procedure.
with soundblaster, there seems to be a conflict with the busmouse. anyone got an idea?

[bkmoore]

Andreas,

I do not currently have Q running, so I am going from memory.

1. The next higher color resolution in 16-bit color worked on my G4 Powerbook. I think it was 1132x864 or something like that.

2. You can use the standard 16-bit soundblaster driver that comes with NeXTSTEP. You just need to set the Soundblaster IRQ to 7 in Configure.app. This version of Q was compiled to use IRQ 7 for the soundcard so it will work.

3. You can use the NE2000 driver for the networking card. I think I found it on the files section of this web site.

4. I never did figure out how to configure Q for bridged networking. So even though my VM was properly configured, Q didn't forward network requests.

5. I never did figure how to get Q to change the host resolution to match the VM resolution in full screen mode. That would have been nice to have.

Again, good luck. It should run very nicely on a G5 Power mac once you get it configured.

Brian Moore

[andreas_g]

i tried setting up sound as you described it, but when nextstep starts up, it just makes a little clicking sound. after that, sound in nextstep does not work and os x's sound is also brocken. (just clicking noises, itunes, etc does not make any sound, restarting resolves the problem in os x)

i could not find the ne2000 driver, but i think setting up network may become a bit too difficult for unexperienced people like me.

[bkmoore]

Andreas,

I'm going to try to build a slightly better version of Q for NeXTSTEP with all the patches. My initial goals are to build a universal binary version, incorporate all NeXTSTEP patches, remove dependencies for MacPorts libraries, and tweek the network settings for bridged networks. I make no promises on any timetables when I'll get this done. I have several projects.

The other project I'm researching is writing a NeXTSTEP 3.3 video driver for Parallels 4.x. If anyone else is working on this already, please let me know so I don't duplicate any efforts.

Mit freundlichen Grüssen,

Brian Moore

[andreas_g]

thanks a lot! i think there are many people here, interested in such an improved build of Q

[bkmoore]

I am getting smart on Q:KJU and its underlying command-line utility Qemu. That being said I don't have a viable patch for the current 0.9.1 snapshot of Q. What I do have is a patch for the current Qemu 0.9.1 SVN Trunk. A lot of thanks to "Madd The Sane" from the Qemu forums for his help. I have managed to get the patch to install and to build a working version of Qemu.

Note, however, that Qemu has changed a lot since Q was released. In order to get Q to use the SVN head of Qemu, a lot of work needs to be done. Work that, unfortunately, is beyond my knowledge. Hopefully Mike Kronenberg will update Q when Qemu releases the next version, which isn't going to be long. At that point, it should be possible to adapt the patch for Q.

I have posted the patch on my public folder at: http://public.me.com/bkmoore

Some basic instructions to building and installing Qemu on Mac OS X.

1. Get the Subversion Package utility at: http://homepage.mac.com/martinott/

2. From the command prompt download the current Qemu source code trunk current revision 669)

svn co svn://svn.sv.gnu.org/qemu/trunk qemu

3. Copy the files: applesmc.c busmouse.c lpc.c from the patch into the /qemu/hw/ sub directory

4. Copy the file currdiff.diff into the /qemu/ directory

5. run the patch utility:

patch -p0 < currdiff.diff

6. Look for errors where the patch failed to apply. I had to go back and add the the following lines to the Makefile.target. You can do a search for .rej (reject) files to find where the patch might not have applied.

OBJS+= lpc.o applesmc.o
OBJS+= busmouse.o

7. Configure the target:
./configure --disable-sdl --disable-aio --target-list=i386-softmmu

8. Build and install the application:

make all

sudo make install

A not of confession. This is as far as I got. I downloaded a miniature linux image to test Qemu and it worked. I then converted my Q NeXTSTEP 3.3 image (.raw) format to a Qemu image, but I am still having issues with the mouse after booting.

Here's what I did:

qemu-img convert -O raw Harddisk_1.raw NS33.img

Then I made some symbolic links to help Qemu find all its components:

ln -s /usr/local/share/qemu/vgabios-cirrus.bin ./vgabios-cirrus.bin
ln -s /usr/local/share/qemu/bios.bin ./bios.bin

Then I used the command line to boot:

qemu -L . -m 32 -hda ns33.img

Hopefully someone here can see where I went wrong, or can tell me what steps I still need to take. I have a working OpenSTEP VM in Parallels, so I am doing this side project more as a public service.

Very Respectfully,

Brian Moore

[andreas_g]

what are the advantages over the existing version of Q?

[kb7sqi]

Hi Brian,
It's good to see "Madd The Sane" is still keeping patches for Qemu. Ok, I tried the "current" svn code + patches on OpenSolaris first. Qemu-0.90 runs flawlessy for me. I dug out my test NEXTSTEP 3.3 image, compiled it & you can see the results on my web site. They don't look good. Something is causing the system hang on boot up. It's late & time for bed, so it's a battle for another day personally. The proper way to start up the system w/ the "current" patches applied is like this:

qemu -M nextpc -m 128 -hda ./ns33.img -k en-us -localtime -soundhw sb16 -net nic -net user

Notice the -M nextpc & the -k en-us. If you don't include those, the busmouse won't work & the keyboard won't work properly as well. I'll give it another shot possible later after waking up on OSX. It's 0410 here now, so I'm beat. Here's the screenshots btw:

http://kb7sqi.dyndns.org/files/screenshots/qemu.test/New.Qemu.Test.1.png

http://kb7sqi.dyndns.org/files/screenshots/qemu.test/New.Qemu.Test.2.png

BTW, andreas_g, normally newer=better. The newer versions of qemu support more hardware, have quite a few bug fixes over 0.90 and also somewhat faster. I'll have to dig the last svn check out I did a while back. It still worked. I'll let you know after sleeping. Take care.