VMware - installing openserver 5.0.x
Yussef ElSirgany
Dear Group,
Has anyone had any luck on installing SCO Openserver 5.0.x on vmware? I have
found only one post with information on pcunix.com/newsgroups but nothing
reproducible or updated!
VMware says that sco openserver/unixware are not supported os'es but people have
been able to install anyway apparently.
--
Thanks and Best Regards,
Yussef.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Yussef M. ElSirgany NY Business Link Corporation
Software Engineer/Unix System Administrator 116 7th Street, Hicksville
NY - 11801 - USA
New viruses and security exploits are discovered Phone: 516-620-2544
every day, ask me about how we can secure your network! Fax : 516-620-0052
Stuart Marshall
> Has anyone had any luck on installing SCO Openserver 5.0.x on vmware? I have
> found only one post with information on pcunix.com/newsgroups but nothing
> reproducible or updated!
>
> VMware says that sco openserver/unixware are not supported os'es but people have
> been able to install anyway apparently.
I tried, without success, to do this about a year ago. I believe that
Open Server will actually /run/ under VMWare but you cannot install
it; it's a while since I tried and I'm sorry I can't remember where
things fell over.
The latest version I tried was 5.0.6, I've not tried 5.0.7.
If you get any further please let me know, it's still on my "want to
do" list :-)
Thanks,
Stuart.
Vetrix
developer machine).
there are 2 big problem of installing directly on virtual machine:
floppy access and detect hardware on first boot.
with a celeron 1.1 ghz and windows 2000 pro, i have installed 5.0.6 and
5.0.7 in very simple way, using BTLD for scsi controller and bootstring.
when i read your post i'm try another installation (to write down a worked
documentation about doing it), but i have new problem.
but now i have upgraded hardware to pentium4 2.66ghz and windows Xp pro, so
i think the problem is related on timing/perfomance issue.
next week i try other solution, and post results on newsgroup.
in same time i try to use VirtualPC 2004 (M$), but there is a big problem
with display driver...
anyone is able to produce a custom installation floppy to simplifies
installation ?
i try to replace kernel on standard floppy with a vmware-working kernel, but
is to big to fit in....
any tricks is welcome.
Mirko
"Stuart Marshall" <stu...@spidersoft.co.uk> ha scritto nel messaggio
news:c1fg04$1hcmu9$1...@ID-142465.news.uni-berlin.de...
Atta Rehman
I was having problems with the display when trying to install SCO
5.0.7 using Microsoft VirtualPC 2004. The following bootstring
helped a bit but I still can't get the virtual hard disk recognised.
SCO OpenServer (TM) Release 5
Boot
: defbootstr cn.primary=vga
It goes through hardware scan as shown bellow problem with the HD
controller:
%adapter 0x0170-0x0177 15 - type=IDE ctlr=secondary dvr=wd
%udi - - - UDI environment
%adapter - - - ha=0 type=usb_msto UDI SCSI HBA
WARNING: hd: no root disk controller was found
hd: a Boot-Time Loadable Driver may be required
WARNING: wd(1) now using polled interface
%cd-rom - - - type=IDE unit=0 ctrl=sec cfg=mst dvr=Srom->wd
mem: total = 130620k, kernel = 55348, user = 75272k
rootdev = 31/7, pipedev = 31/7, dumpdev = <none>
kernel: Hz = 100, i/o bufs = 37092k (high bufs = 36068)
Press <Enter> to begin installation
Any ideas what could be causing wd driver not to load properly..?
Vetrix
i'm bypass the display problem (with 506) on virtual pc usig oss653 and
bootstring "link=ivga",
i think your solution work only with 5.0.7.
but "wd" driver dont recognize primary ide controller (and related hard
disk) and installation stop (no root hard disk).
this append also on vmware (in vmware sco running on emulated SCSI hard disk
....) when use IDE driver.
i try to use update wd driver found on
http://www.sco.com/support/update/download/osr507list.html, wich have much
debug support with bootstring:
"defbootstr link="ivga wd506" wd.debug=i" but hard disk is not recognized
too.
i add "adapter=wd(0x0170,14,0)" without success.
at this moment, with a DOS utility, i try to detect cylinder/head/sector of
virtual hard disk, to use in bootstring.
defbootstr biosgeom=(cyl,head,sector)
I will make you to know if is that works..
i have olso try to install on ide hard disk in standard way and then use
vmware/virtual pc to "run" from this phisical disk (is the tricks used for
install on vmware with SCSI hard disk) without success.
any "wd driver" guru contribute ?
"Atta Rehman" <are...@bond.co.uk> ha scritto nel messaggio
news:67d05ca7.04030...@posting.google.com...
Bela Lubkin
> i'm bypass the display problem (with 506) on virtual pc usig oss653 and
> bootstring "link=ivga",
> i think your solution work only with 5.0.7.
> but "wd" driver dont recognize primary ide controller (and related hard
> disk) and installation stop (no root hard disk).
> this append also on vmware (in vmware sco running on emulated SCSI hard disk
> ....) when use IDE driver.
> i try to use update wd driver found on
> http://www.sco.com/support/update/download/osr507list.html, wich have much
> debug support with bootstring:
> "defbootstr link="ivga wd506" wd.debug=i" but hard disk is not recognized
> too.
Does it produce any debug output? Try "wd.debug=iu", post the resulting
debug output.
> i add "adapter=wd(0x0170,14,0)" without success.
> at this moment, with a DOS utility, i try to detect cylinder/head/sector of
> virtual hard disk, to use in bootstring.
> defbootstr biosgeom=(cyl,head,sector)
> I will make you to know if is that works..
It won't help.
> i have olso try to install on ide hard disk in standard way and then use
> vmware/virtual pc to "run" from this phisical disk (is the tricks used for
> install on vmware with SCSI hard disk) without success.
That probably won't help either. "wd" will still trip over whatever
it's tripping over. But go ahead and try it anyway, there's at least a
small chance of success.
>Bela<
Atta Rehman
> Vetrix wrote:
>
> > i'm bypass the display problem (with 506) on virtual pc usig oss653 and
> > bootstring "link=ivga",
> > i think your solution work only with 5.0.7.
> > but "wd" driver dont recognize primary ide controller (and related hard
> > disk) and installation stop (no root hard disk).
> > this append also on vmware (in vmware sco running on emulated SCSI hard disk
> > ....) when use IDE driver.
> > i try to use update wd driver found on
> > http://www.sco.com/support/update/download/osr507list.html, wich have much
> > debug support with bootstring:
> > "defbootstr link="ivga wd506" wd.debug=i" but hard disk is not recognized
> > too.
>
> Does it produce any debug output? Try "wd.debug=iu", post the resulting
> debug output.
>
Installing SCO 5.0.7 on a Microsoft VirtualPC 2004 (Build 582)
Using updated version of the wd(HW) driver btld
SCO OpenServer(TM) Release 5
Boot
: defbootstr link=wd wd.debug=iu cn.primary=vga
%serial 0x02F8-0x02FF 3 - unit=1 type=Standard nports=1 base=8 16550A/16
%floppy 0x03F2-0x03F7 6 2 unit=0 type=135ds18
%console - - - unit=vga type=0 num=12 scoansi=1 scroll=50
%console - - - unit=cga type=2
%kbmouse 0x0060-0x0064 12 - type=Keyboard|PS/2 mouse (wheel) id=0x03
wd: PCI bus/dev/func 0/7/1, vend/dev 8086/7111, prog_if 80, BMIBA 0000FFA1
wd: controller supports UDMA mode 33
wd 0/0: IDENTIFY_DEVICE: Status 58, Error 00
wd 0/0: non-ATAPI device present
wd 0/0: Max MBoard UDMA mode=2, Drive does not support UDMA
wd 0/0: BIOS disabled UDMA for drive
wd 0/1: IDENTIFY_DEVICE: Status 51, Error 04
wd 0/1: ATAPI_IDENTIFY: Status 58, Error 00, ATAPI = yes
%adapter 0x01F0-0x01F7 14 - type=IDE ctlr=primary dvr=wd
%udi - - - UDI environment
%adapter - - - ha=0 type=usb_msto UDI SCSI HBA
WARNING: hd: no root disk controller was found
hd: a Boot-Time Loadable Driver may be required
WARNING: wd(0) now using polled interface
%cd-rom - - - type=IDE unit=0 ctlr=pri cfg=slv dvr=Srom->wd
mem: total = 130620k, kernel = 55392k, user = 75228k
rootdev = 31/7, pipedev = 31/7, dumpdev = <none>
kernel: Hz = 100, i/o bufs = 37068k (high bufs = 36044k)
Any ideas..?
Atta
Bela Lubkin
Try adding "wd.udma=off", any better? Also add "g" to the debug string;
so:
Boot
: defbootstr link=wd wd.debug=iug wd.udma=off cn.primary=vga
Any better? If not, post the new debug output.
>Bela<
Atta Rehman
Thanks for your response Bela. I'm afraid still no joy adding
wd.udma=off to the bootstring:
defbootstr link=wd wd.debug=iug wd.udma=off cn.primary=vga
%floppy 0x03F2-0x03F7 6 2 unit=0 type=135ds18
%console - - - unit=vga type=0 num=12 scoansi=1
scroll=50
%console - - - unit=cga type=2
%kbmouse 0x0060-0x0064 12 - type=Keyboard|PS/2 mouse (wheel)
id=0x03
wd: PCI bus/dev/func 0/7/1, vend/dev 8086/7111, prog_if 80, BMIBA
0000FFA1
wd: controller supports UDMA mode 33
wd 0/0: IDENTIFY_DEVICE: Status 58, Error 00
wd 0/0: non-ATAPI device present
wd 0/0: Max MBoard UDMA mode=2, Drive does not support UDMA
wd 0/0: BIOS disabled UDMA for drive
wd 0/0: UDMA disabled by bootstring
wd 0/1: IDENTIFY_DEVICE: Status 51, Error 04
wd 0/1: ATAPI_IDENTIFY: Status 58, Error 00, ATAPI = yes
%adapter 0x01F0-0x01F7 14 - type=IDE ctlr=primary dvr=wd
%udi - - - UDI environment
%adapter - - - ha=0 type=usb_msto UDI SCSI HBA
WARNING: hd: no root disk controller was found
hd: a Boot-Time Loadable Driver may be required
WARNING: wd(0) now using polled interface
%cd-rom - - - type=IDE unit=0 ctlr=pri cfg=slv
dvr=Srom->wd
mem: total = 130620k, kernel = 55392k, user = 75228k
rootdev = 31/7, pipedev = 31/7, dumpdev = <none>
kernel: Hz = 100, i/o bufs = 37068k (high bufs = 36044k)
Atta
Atta Rehman
OpenServer on Microsoft VirtualPC 2004.. as this thread is for VMWare.
Atta
are...@bond.co.uk (Atta Rehman) wrote in message news:<67d05ca7.04030...@posting.google.com>...
TightCode
1. Download http://www.mylex.com/pub/multimaster/mmunix.exe
2. Extract mmunix.exe.
3. Type "unix a:" to create BTLD diskette.
4. Create VMware virtual machine with type "Other".
5. Add SCSI disk (TID=0), IDE disk (0:0), IDE CD (0:1)
6. Start VM and set BIOS to boot from CD.
7. At "Boot:", type "restart link=blc Sdsk=blc(0,0,0,0)
Srom=wd(0,0,0,0)"
8. At "Please insert the fd(65)blc volume and press<Return>", mount
BTLD diskette.
9. At "Please enter
'r' if you wish to try replacement
'a' if you want to use character magor 6 [default]
or 'q' to quit:",
type "a".
10. At "Please select the floppy device you are using:
(1) /dev/fd0
(2) /dev/fd1"
select "2", then choose "b (Abort BTLD load, but continue
installation)".
11. After installation and reboot at "Boot:", type "fd(64)unix
link=blc root=hd(42) swap=hd(41)"
12. Repeat steps 8 and 9.
13. Login to single user mode.
14. Type "mount /dev/fd0135ds18"
15. Type "btldinstall /mnt"
btldinstall /mnt --> blc
--> Do you want to replace it with the version in
blc? y
--> Do you want to preserve the host adaper
configure
information? n
--> y?
P.S. Originally from http://www.chinaunix.net/bbsjh/4/11249.html
Bela Lubkin
> Installing OpenServer 5.0.6 onto VMware Workstation -
>
> 1. Download http://www.mylex.com/pub/multimaster/mmunix.exe
This URL is stale. www.mylex.com redirects to a sub-page of
www.lsilogic.com; lsilogic.com seems to cover Mylex RAID adapters but
has little to no mention of BusLogic. google finds:
http://www.lsilogic.com/files/support/mylex/hbas/mmunix-readme.txt
and related pages; but none of them seem to point to actual downloadable
files.
A "blc" driver is included in the default OSR5 ISL kernel on the CD-ROM.
What happens if:
> 7. At "Boot:", type "restart link=blc Sdsk=blc(0,0,0,0)
> Srom=wd(0,0,0,0)"
... here you use "defbootstr Sdsk=blc(0,0,0,0) Srom=wd(0,0,0,0)",
without the BTLD? What kind of BusLogic HBA does VMware emulate -- is
it something newer than the OSR5 internal driver supports?
>Bela<
TightCode
> TightCode wrote:
>
> > Installing OpenServer 5.0.6 onto VMware Workstation -
> >
> > 1. Download http://www.mylex.com/pub/multimaster/mmunix.exe
>
> This URL is stale. www.mylex.com redirects to a sub-page of
> www.lsilogic.com; lsilogic.com seems to cover Mylex RAID adapters but
> has little to no mention of BusLogic. google finds:
>
> http://www.lsilogic.com/files/support/mylex/hbas/mmunix-readme.txt
>
> and related pages; but none of them seem to point to actual downloadable
> files.
>
Here is a link that still works:
http://ftp.isu.edu.tw/pub/Hardware/mylex/multimaster/mmunix.exe
David
contains extremely detailed instruction for installing OpenServer
under VMware.
I hope this helps.
Stuart J. Browne
"David" <Goo...@ComputerLandInc.com> wrote in message
news:7f9f3864.04040...@posting.google.com...
Fantastic looking instructions! I'll give it a try out a bit later.
Bela Lubkin
> Here is a link to my site (http://David.ComputerLandInc.com), which
> contains extremely detailed instruction for installing OpenServer
> under VMware.
I recently downloaded the 30-day eval of VMWare Workstation so I could
play with this stuff. My experiences with it were similar to yours,
with one big simplifying exception.
Your web page barely mentions any version numbers. You mention VMWare
Workstation "4" and no OpenServer release information at all.
The VMWare Workstation eval that was available when I downloaded was
"4.5.1 build-7568". I installed it on a Windows XP SP1 system. I then
did various test installs of OpenServer Release 5.0.7.
It's been a couple of weeks since I did this, so the details aren't as
fresh as I'd like, but here's a general sense of what I did:
- new virtual machine, "other", 128MB RAM, IDE virtual hard disk
- boot OSR507 CD
- install normally (no bootstrings, no BTLDs)
- once installed, `scoadmin video`, choose "VESA" driver and a
suitable resolution
The key bit here is that I had no trouble between the OSR507 "wd" IDE
driver and VMWare's emulation of IDE controllers/drives. This may be an
enhancement made between VMWare 4.0 and 4.5.1.
I did fiddle with SCSI a little bit. VMWare Workstation 4.5.1 offers
two SCSI host adapter emulations: BusLogic BT958 and LSI Logic 53c1020.
A driver for BT958 is present in the OSR507 boot CD kernel, but it's a
defective build of the driver and does not support PCI HBAs. That's why
you need a BTLD. The BTLD appears to work, but I didn't attempt
installation beyond the point of recognizing the hard disk.
A driver for LSI 53c1020 is available from www.lsilogic.com ("lsil").
Loading this as a BTLD, under OSR507, VMWare 4.5.1, XP SP1, fails. I
don't have notes on it but basically VMWare announced an attempt to run
an illegal instruction.
No big deal, if you want to emulate SCSI just use the BusLogic choice.
It shouldn't make much difference that you're stepping down from an
Ultra320 to an UltraWide controller, since there are no physical disks
and physical transmission paths being narrowed.
I also had no trouble with high video resolutions. The windows box is
running its native video at 1152x864 with 32-bit color, so I told OSR5
to use 1152x864 16-bit color (the VESA driver didn't offer 32-bit
color). The resulting display has to be scrolled when seen through a
VMWare window, but when I display it fullscreen, it exactly fills the
screen, looks just like native OSR5.
Tip: go to Preferences -> Hot Keys, set the combination to
Ctrl-Shift-Alt. This allows OSR5's multiscreen switch sequences
(Ctrl-Alt-F1 etc.) to work.
A few glitches. One: the first time I ran `mkdev graphics` and
selected VESA, it all worked nicely. Later runs get a coredump in the
utility that reads VESA mode information, so I have had to resort to
hand-editing the file that assigns modes to console multiscreens
(/usr/lib/grafinfo/grafdev). The significant line in my copy reads:
/dev/tty02:vesa.svga.vbe.1152x864-16
Probably for the same reason, when I reboot the virtual machine it
reverts to IBM VGA 640x480 16-color. I have to copy my hand-modified
grafdev file over the one the system reverted.
Two: the mouse resolution is weird (not at all smooth).
Three: the mouse _sometimes_ goes insane and I have to reboot the
virtual machine to fix it.
Four: telling VMWare to go fullscreen works fine in graphics mode, but
if I do it on a text multiscreen, the monitor tries to lose sync. It
puts up a self-generated display saying that the signal from the
computer is outside its sync range: "OUT OF FREQUENCY RANGE / Attention
/ Out of range / H:29.1KHz 69.9Hz".
Worst of all: I sent a detailed message to VMWare support about these
and other issues, and -- as I have experienced over all the years since
VMWare first came on the market -- I was soundly ignored.
>Bela<