I've actually gotten NextStep 3.3 to work (and at 1280x1024 @ 32-bit) in VMWare Workstation 6 (Vista Ultimate x86 host); now it's down to picking nits.
First nit: setting up the networking. I have the AMD PCnet32 driver loaded currently and have VMWare itself set to use NAT; how do I configure the HostManager to use DHCP? (For that matter, how do I get to login as root, which is required?)
Second nit: configuring audio support. The Sound Blaster 16 driver installed without a hitch. (If you are using the AMD PCnet driver, move the IRQ setting for it from 5 (the default, which conflicts with the SB16), to 10 (VMWare's default, which conflicts with nothing).) Now I need to find some audio files to play to test out the support.
So far, that's pretty much it for the nits.
Quote from: "PGHammer"
how do I configure the HostManager to use DHCP? (For that matter, how do I get to login as root, which is required?)
I don't think 3.3 supported DHCP out of the box. There are some add-ons with some checkered history that can do it, however.
Quote from: "PGHammer"
Now I need to find some audio files to play to test out the support.
Haven't done a white install in a very long time but with black, the initial account gets a mail file with email from Steve Jobs including a voice attachment welcoming you to NeXT. There's your audio...
Quote from: "cubist"Haven't done a white install in a very long time but with black, the initial account gets a mail file with email from Steve Jobs including a voice attachment welcoming you to NeXT. There's your audio...
On white hardware, it's only a NeXTstep cubes image, some text, a URL image, and a signature.
Eric
Quote from: "ericj"On white hardware, it's only a NeXTstep cubes image, some text, a URL image, and a signature.
Sounds likely. Still, there should be a few .snd files around the system for UI feedback purposes. (I never checked to see if the NeXT printer vocal status reports were shipped with white....)
TJL's port of DHCP to NS 3.3 did the trick (I'm posting this via OmniWeb 3 beta 6 on the NS 3.3 VM). So the nits have been picked.
Quote from: "PGHammer"Firt nit:.... I have the AMD PCnet32 driver loaded currently....
You may want to try the VMXNet driver with VMware 6. As far as I know the AMDPCnet32 driver stopped working with VMware 5 (it did for me that's why I wrote the new one).
AMDPCnet32 loads okay and detects the chip but will not transport any network packages for the newer versions.
Quote from: "PGHammer"
Second nit: configuring audio support. The Sound Blaster 16 driver installed without a hitch.
VMware emulates an Ensoniq ES1371 sound chip so the normal SoundBlaster driver (ISA) shipped with NS3.3 will not work with that. Use my SoundBlaster16PCI driver instead. It works under VMware 4.5 up to 5.0 (and I think 6 too) with OpenStep. Some people reported it works with NS3.3 some had problems with that so you have to try yourself.
Quote from: "PGHammer"
(If you are using the AMD PCnet driver, move the IRQ setting for it from 5 (the default, which conflicts with the SB16), to 10 (VMWare's default, which conflicts with nothing).)
There should be no interrupt conflict between both chips at all since both are implemented as PCI devices by VMware and configured to different interrupts by the BIOS of the virtual machine.
Quote from: "PGHammer"
Now I need to find some audio files to play to test out the support.
Have a look at "/NextLibrary/Sounds" there are some of the system sounds you can use for testing purposes.
Both of the mentioned drivers can be found on my webpage:
http://mitglied.lycos.de/morgon_de
Quote from: "Morgon"Quote from: "PGHammer"Firt nit:.... I have the AMD PCnet32 driver loaded currently....
You may want to try the VMXNet driver with VMware 6. As far as I know the AMDPCnet32 driver stopped working with VMware 5 (it did for me that's why I wrote the new one).
AMDPCnet32 loads okay and detects the chip but will not transport any network packages for the newer versions.
Quote from: "PGHammer"
Second nit: configuring audio support. The Sound Blaster 16 driver installed without a hitch.
VMware emulates an Ensoniq ES1371 sound chip so the normal SoundBlaster driver (ISA) shipped with NS3.3 will not work with that. Use my SoundBlaster16PCI driver instead. It works under VMware 4.5 up to 5.0 (and I think 6 too) with OpenStep. Some people reported it works with NS3.3 some had problems with that so you have to try yourself.
Quote from: "PGHammer"
(If you are using the AMD PCnet driver, move the IRQ setting for it from 5 (the default, which conflicts with the SB16), to 10 (VMWare's default, which conflicts with nothing).)
There should be no interrupt conflict between both chips at all since both are implemented as PCI devices by VMware and configured to different interrupts by the BIOS of the virtual machine.
Quote from: "PGHammer"
Now I need to find some audio files to play to test out the support.
Have a look at "/NextLibrary/Sounds" there are some of the system sounds you can use for testing purposes.
Both of the mentioned drivers can be found on my webpage: http://mitglied.lycos.de/morgon_de
I'm using the VMXNet, VMMouse, and SB16PCI drivers, and the VMWare SVGA driver (all from your page) with VMWare 6. However, I'm curious if they work with VirtualBox (which emulates the same hardware).
When I try to install NS3.3, I'm not able to select the EIDE and ATAPI driver for the CD-ROM. It appears only SCSI CD-ROM will work. However the BusLogic PCI SCSI driver does not appear to work. I get repeating messages: "Resetting SCSI Bus..." "BLC timeout".
How did you get NS3.3 to install?
Quote from: "shanghaiscott"When I try to install NS3.3, I'm not able to select the EIDE and ATAPI driver for the CD-ROM. It appears only SCSI CD-ROM will work. However the BusLogic PCI SCSI driver does not appear to work. I get repeating messages: "Resetting SCSI Bus..." "BLC timeout".
How did you get NS3.3 to install?
Due to a rather odd quirk, you can't install the Dual PCI IDE driver (from the 3.3 Beta Drivers floppy image) *first*, so you have to fake it out by installing a SCSI driver (not necessarily a *correct* one; I use the Adaptec 2940 PCI SCSI driver from the Boot Drivers floppy image) ahead of it.
So the correct order is: Boot Drivers floppy, install fake SCSI driver, then swap in Beta Drivers floppy, then go to the second page of drivers from this floppy (option 7) and select the Dual PCI IDE driver (option 2 on that page), then select option 1 to continue (however, don't take the floppy out; you'll need it after you reboot from the hard drive).
Quote from: "PGHammer"
I'm using the VMXNet, VMMouse, and SB16PCI drivers, and the VMWare SVGA driver (all from your page) with VMWare 6. However, I'm curious if they work with VirtualBox (which emulates the same hardware).
VMMouse is unlikely to work under any other emulator than VMware as it makes copious use of special functions to communicate with VMware (the same functions the VMtools use) for getting the mouse coordinates.
VMXNet uses some of the additions VMware made to the AMDPCnet32 chip and I did not ponder over the various parts when porting that driver. So it may work with other emulators emulating the same card but I don't know if it would.
The SVGA driver is not written by me but I had a look at it once and think it uses some of the VMware specific calls too (but I don't remember right now).
The soundblaster driver should work with every ES1371 compatible chip as I wrote it for a real soundblaster 16 PCI card I own. That it suits the card emulated by VMware is only a side effect that I wasn't aware of and had to find out from usenet news a while after I published the driver on peanuts :-)
Thanks for the help on this! I have got past the SCSI CD-ROM issue, but now when the install starts to read my CD-ROM, it prints out:
Load of /etc/mach_init, errno 2, trying /etc/init
Load of /etc/init failed, errno 2
Does this mean my CD-ROM is bad or something?
I've put the screenshot here:
https://geneticmail.com/scott/nextstep-33-init-failed.png
Quote from: "shanghaiscott"Thanks for the help on this! I have got past the SCSI CD-ROM issue, but now when the install starts to read my CD-ROM, it prints out:
Load of /etc/mach_init, errno 2, trying /etc/init
Load of /etc/init failed, errno 2
Does this mean my CD-ROM is bad or something?
I've put the screenshot here: https://geneticmail.com/scott/nextstep-33-init-failed.png
You've got the Developer 3.3 disc in. You need to put in the User 3.3 disc to install.
Eric
I purchased NeXTStep 3.3 Developer edition about 13 years ago.. all I can find from it are 3 original 3.5" floppy disks and 5 CD-ROMs. One is labled NEXTSTEP DEVELOPER, then I've got ENTERPRISE OBJECTS, THIRD PARTY PRODUCTS,. Lighthouse Design Tools for Enterprise, Co-Xist.
I thought the one labeled NEXTSTEP DEVELOPER was the OS disk... I don't have a "User" disk. Blarrrgh.
Quote from: "shanghaiscott"I purchased NeXTStep 3.3 Developer edition about 13 years ago.. all I can find from it are 3 original 3.5" floppy disks and 5 CD-ROMs. One is labled NEXTSTEP DEVELOPER, then I've got ENTERPRISE OBJECTS, THIRD PARTY PRODUCTS,. Lighthouse Design Tools for Enterprise, Co-Xist.
I thought the one labeled NEXTSTEP DEVELOPER was the OS disk... I don't have a "User" disk. Blarrrgh.
If I recall correctly, NeXTstep User had to be purchased separately from NeXTstep Developer (bringing the total to about $6,000). Also, there were no floppies included with NeXTstep Developer, so are you sure you didn't lose a disc?
Eric
I purchased NS 33 developer via a university student program. I recall that I paid about $350 for the whole set. It included the installation CD as well as all the developer goodies (including enterprise objects.)
I just took some photos of my original media with the crummy camera in my cell phone:
https://geneticmail.com/scott/ns-33-dev-media-01.jpghttps://geneticmail.com/scott/ns-33-dev-media-02.jpghttps://geneticmail.com/scott/ns-33-dev-media-03.jpgIf anyone has the "user" CD could they let me know? scott at geneticmail.com
