... do I get these driver files onto the virtual machine...??
Help! I'm stuck. I've managed to get NeXTSTEP 3.3 running under VMware Workstation 6, and all is cool, well, except the mouse, video, sound, networking... etc - normal stuff by the looks of it.
So I'm trying to get that sorted, and have a load of new drivers to try.
But how do I get them actually onto the virtual machine in the correct format for NeXTSTEP to use?
I've no floppy disk drive in my (Vista) PC. I've tried burning them to a CD, and accessing the CD via the VMware virtual drive, but although the files are there, it's almost as if they're missing an attribute that makes them 'driver' files. Is Windows munging something?
For example, I burn the CD from Nero under Vista, with the VMMouse and VMXNet drivers unzipped into their respective folders, and when I access them under NeXTSTEP they just open - no start of Configure.app...
If I try and do it manually - i.e., start Configure.app, remove driver and add a new one, the 'OK' button is always grayed out!
I've read the 'FAQ-OpenStepOnEmulators' document, but this just says to transfer the files onto floppy/cd, which I'm doing - although evidently not correctly...
Has anyone got any ideas? Or can you point me in the right direction?
Many thanks!
Quote from: "simonc99"I've tried burning them to a CD, and accessing the CD via the VMware virtual drive...
There is no need to really burn the CD. In VMware Workstation you can use the iso image generated by your burning program as well.
Quote from: "simonc99"
... but although the files are there, it's almost as if they're missing an attribute that makes them 'driver' files. Is Windows munging something?
Under NeXTStep drivers are organized in folders with the extension ".config". The whole folder is the driver and contains all files needed (kernel modules, configuration file, interface files for Configure.app, tools, ...). All these files need to be kept together in the respective driver folder.
There is no special attribute that identifies a folder as driver. If the folder name has the extension ".config" the system will open it with Configure.app which in turn will install the driver to the system driver folder.
Quote from: "simonc99"
For example, I burn the CD from Nero under Vista, with the VMMouse and VMXNet drivers unzipped into their respective folders, and when I access them under NeXTSTEP they just open - no start of Configure.app...
When creating the CD with windows you have to make sure that it creates the RockRidge extension to ISO 9660 or NeXTStep will be unable to read the long filenames from the CD.
Maybe you should try to put the driver archive onto your CD(-image) instead of the extracted files and extract the archive under NeXTStep after mounting the virtual CD. That way Windows has no chance to mess up the filenames and folder structure of the driver files.
Hope these hints help to solve your problem.
Morgon
That's great - all up and running. You were absolutely correct Morgon, so thanks for pointing all that out.
For future reference, here's what I did...
Downloaded the drivers from appropriate sites (links are available on this forum, so I won't go into that).
Put them all in one folder under windows.
Used 'MagicISO' to drag the folder into the files pane.
Clicked 'properties' on the file menu
Changed the appropriate attributes for the CD image :
In the 'ISO' tab, make sure the CD File System is ISO 9660 with Rock Ridge (that's all - uncheck everything else)
the File / Directory names section should be ISO 9660
Then OK it, go back to the 'file' menu, and save as. Choose to save as 'ISO' format, then voila, all done.
Works a treat - thanks so much for your help (and your drivers) Morgon.
Now up and running in 1280x1024 32 bit, with only one issue - in Configure.app, no matter what I set the mouse 'Desktop Layout' to, it seems to revert to 480 in the 'h' plane. The 'w' plane is fine - it stays at whatever I set it to. This makes the vm a little difficult to use, as I can't get the mouse pointer to the bottom half of the screen!
Any ideas?
Thanks again.
Well, that little problem is solved - seems like user error - i.e., me not pressing the enter button after putting in the plane size.
Guess windows has made me lazy...!
Thanks again for all your help - all is up and running now. I could put the cd image with all the drivers etc (in the proper format to be read by vmware!) somewhere if anyone has got a suggestion where?
Thanks very much again
Good to hear you worked it out and got everything installed :D
Quote from: "simonc99"Well, that little problem is solved - seems like user error - i.e., me not pressing the enter button after putting in the plane size.
Yes, that's a little bug the configuration interface of VMMouse still has. And as it would take quite a bit of programming to get rid of that without getting in other annoying effects I will leave it as it is ;)