OpenSTEP 4.2 Doesn't Run with 4 - VT-x may be the Problem?

S

spetznatz

Hunter
OS 4.2 worked flawlessly under Pllels 3.x. However, in Pllels 4.0, VT-x is turned on by default and can't be turned off. OS 4.2 needs VT-x to be turned off to run.

PLEASE give us this option back.

Or let us run Pllels 3 and 4 on the same machine.
 
Just noticed, I get the message (after OS 4.2 starts to boot and after memory sizing)

"VBE Mode 305 not supported. Using VBE mode 257 instead." That wasn't there with Pllels 3.0.
 
I think VBE is the display driver, try playing with video memory values under Parallels.
 
Thanks, Specimen -- but I think the VT-x problem is at the root of it all. At least It needs to be eliminated first.
 
Thanks, John --

It nearly worked...

The boot process progressed much further, but still hangs when it gets to the 'power management is enabled' part.

Is there any chance of a fix? In know OS 4.2 isn't an officially supported OS.
 
Hmmmm. No Joy.

Now it doesn't get to the 'Power Management is enabled' step. It hangs at the step before ('Check and re-set the date!').

If I could use version 3 on the same machine as 4 this wouldn't be a problem... I don't need multi-processing and high memory limits to run NeXTSTEP.
 
this works for me with OpenStep 4.2

in CPU -System flags: (without the quotes)

"hvtsupport=0,acpi=0,apm.enable=0"

an with an texteditor in the pvs-File change

"<EnableVTxSupport>1</EnableVTxSupport>"

to

<EnableVTxSupport>0</EnableVTxSupport>

32 MB VideoRAM and under configure.app in Openstep use 1280x1024/888

Regards Peter
 
this works:
in CPU System flags: hvtsupport=0,acpi=0,apm.enable=0
Change in pvs-file: "<EnableVTxSupport>1</EnableVTxSupport>" to "<EnableVTxSupport>0</EnableVTxSupport>"
you need 32MB VRAM an in configure.app use 1280x1024/888

Regards Peter
 
more info

maybe the screenshots from openstep will help

you can boot into Default mode in Openstep with "config=Default" in the boot-Screen. This always works for me.
Sometimes with my settings above Openstep will "hang" on Boot. PD3 worked better here.

Peter
 

Attachments

  • Screenshot 1.png
    Screenshot 1.png
    274.5 KB · Views: 43
  • Screenshot 2.png
    Screenshot 2.png
    261.5 KB · Views: 33
  • Screenshot 3.png
    Screenshot 3.png
    268 KB · Views: 31
Well, may be it is from my MBP CD 1.83 2 GB of RAM, but I have installed OpenStep4.2 without those flags
I just selected to load drivers
776
and
7774
OS type Other,
OS version other
Video 32 mb
Memory 128 mb
 
John,

I have tried for some time to get Openstep 4.2 to run in PD4. I've tried all the drivers on the Openstep install disks and the "beta" releases. It gets to the point that it loads mach_init and dies with errno 14.

It also dies at that point when using my image from PD3 (which works nicely in PD3). It also dies there when using "config=Default".

I don't understand what you mean by "loading drivers 776 and 7774". Are those Openstep drivers? Where did you get them? Or are they things one loads in parallels? If so, how do you load them? What sort of drivers are they?

Thanks,
- David
 
Drivers are from Apple site

776 I mean, pass first driver screen 7, second hit 7, on 3rd select 6
and also my typo
on the second sequence is 7772
Here are my full steps
1. Start Parallels Desktop
2. Select File - New Virtual machine
3. Click Continue on Introduction page
4. Select CD/DVD image and point to OpenStep 4.2 ISO image
5. Select OS type - "Other"
6. Select OS version - "Other"
7. Select Custom installation type
8. Specify Name and Location
9. Click Done
10. Click Configure in Virtual machine window
11. Set Memory to 128 mb
12. Make sure Video is set to 32 mb
13. Make sure floppy disk controller is Enabled and Connected
14. Specify 4.2_Install_Disk.img in image path
15. In Boot Order move Floppy Disk to first position
16. Click OK and start Virtual machine
17. insert Driver installation disk
18. Select 776 in device drivers (clicking enter)
EIDE and ATAPI Device Controller (v 4.01)
19. Select 7772 in device drivers (clicking enter)
IDE Disk Controller (v 4.01)
20. Continue with installation.
 
John,

I'm sorry, but this is not what I wanted to read here. I had an image which took quite a while to install, working perfectly and smooth with PD3. I'd really appreciate if I could continue to use it with PD4, and not start a new installation from scratch!

Please don't tell me that I have to downgrade PD.

Regards,
Markus
 
You must log in or register to reply here.
Back
Top