DR2 runs just fine.... but i never found anything about DR1.
:)
I have now installed DR1/intel into VMWare server 1.03 .
I am now able to get much further into the install process. The CD is definetly being read. My iSO image is good!
The problem now is that the installation stops and asks for input.
quote:BOOT_DISK
IDE DISK #1 (Type 225) - 1023 MB
WHICH_DISK
---->
If I type "1", I get the following:
quote:
FDISK_MENU1 not found
And it won't accept any more input
Any idea ?
Someone has another set of DR1/intel floppies images for me ?
Thanks
The problem is solved using a new set of floppies from DR1. Everything is just fine now. DR1 running inside VMWARE server 1.03 in this moment.
:)
I'm trying to get this set up just today.
I have DR1 installed in VMware (Fusion, if it matters), and now I'm working on getting the VMware drivers installed. I figured I'd try the DR2 network/mouse/display drivers, but the CD doesn't mount in single user mode.
Here's what happens for me:
# mkdir /mnt
# mount -t cd9660 /dev/sd0a /mnt
sd0a: Read attempt with no valid label
cd9660: Invalid argument
#
I should note that I have the CD image connected when I boot the VM.
Did you get past this part?
Hi everyone!
I've installed DR1 on VMware 6.5 Workstation.
The installation process went OK. The only problem was that after booting up the newly-installed DR1, there was no assistent as in DR2, no host manager or configure.app, so I couldn't set up the vmware drivers for the display, mouse or network and I couldn't set the network itself.
If i have some spare time this weekend I will build a new VMware DR1 and will send some screenshots of the above described ;)
All the floppy images and the CD image work fine, though :) !
Well, I had another idea: take the VMDK of my DR1 install, and attach that to a DR2 VM to put the drivers on it. Then, move the VMDK back to the DR1 VM.
After all that, I now have a DR1 system with working video & mouse. The only problem that remains is the network. I have been able to get Configure.app to see the network adapter, and it offers to install VMXnet.config, but it kernel panics upon reboot. I have tried all 3 network adapter types in the vmx file (see
http://www.sanbarrow.com/vmx/vmx-network.html), and have had success with none of them.
Quote from: "eagle"I have tried all 3 network adapter types in the vmx file (see http://www.sanbarrow.com/vmx/vmx-network.html), and have had success with none of them.
The network type has no effect on the virtual hardware as seen by the guest system. It's just how the host side mapping of the network card is done. For example NAT network runs an additional DHCP server on the virtual network.
Therefore the difference for the client is the number and type of other "computers" (real ones for bridged network or "virtual" ones for the other types) available in the virtual network (dhcp, gateway) or not.
Hi Morgon. I'm talking about the different network adapters (e1000, vmxnet, and vlance), not the topologies (bridged, hostonly, and nat).
If memory serves, DR1 properly detects the VMware network adapter if vmxnet is set as the network adapter in the vmx file, but no adapter is selected for the other options. And maybe it's vlance that works.
I have only tried the bridged topology setting, since I want this to appear as a real host on my network.
Quote from: "eagle"Hi Morgon. I'm talking about the different network adapters (e1000, vmxnet, and vlance), not the topologies (bridged, hostonly, and nat).
Oops. Should have checked the text on the linked site more closely :oops:
The vlance with the AMDPCNet32 driver stopped working with OS4.2 under VMwareWorkstation 4.52 (or 5?). That's why I initially wrote the VMXNet driver to get networking going again. Think VM didn't have the option for other virtual network hardware at that point.
vmxnet is based on the vlance after all and uses that mode before the driver switches it to the vmxnet mode during initialisation.