• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

Migrate OS/2 to VMware

Started by jschang, 2011.07.06, 09:53:11

Previous topic - Next topic

jschang

dear all
I migrate OS/2 Wrap 4.0 to VMware(ESX 4.1) by backup OS/2 disks and restore to VMware recently.
It looks well, but network. I set two NICs in OS/2 with AMD PCNet driver
(there's also two virtual NICs setting for the OS/2)
When OS/2 boots, it always can't found the second NIC.
Does anyone knows how to solve it? thanks.

ivan

Does the NIC driver appear twice in Config.Sys?  Each instance of the NIC must have its own driver or it will not be seen or work.

ivan

jschang

ya...there are two lines about AMD PCnet Driver in CONFIG.SYS.
When OS/2 boots, 1st NIC driver load OK....but 2nd NIC driver load fail (PCI Scan specified, device not found.....)
ps. I have assigned two virtual networks for OS/2 on VMware

jschang

I've found the root cause......Just update OS/2 AMD PCNet NIC driver to 4.08, and All's OK.

ivan

Thanks for posting your solution that may help others.

ivan

RobertM

Quote from: jschang on 2011.07.14, 05:37:30
I've found the root cause......Just update OS/2 AMD PCNet NIC driver to 4.08, and All's OK.

The older driver in all probability (from the message, if it was properly used) could have had identifying information specified (method indicated below).




While I know you've got this issue solved (and others who may use that card can follow your method to resolve it), this issue also applies to a variety of other NICs.

For anyone else who runs into such:

The required info could be added via MPTS (or directly into the config.sys file - which requires knowledge of how the parameters are used). Especially if an IRQ ends up being shared, such info is needed with certain drivers. That info is usually an assigned address range, or a slot ID (in some format determined by the driver, ie: by number or by the way the chipset identifies it).

It's really as simple as using MPTS to select each card, modify it's properties, look for the slot identifier field, and enter in the correct information. Most cards/drivers that require such will inform you (on the MPTS settings page, or via the help pop-up) what format is needed.

Now, there are a few cards that simply wont work under OS/2 (and possibly other operating systems) when 2 or more are installed... in such cases, you wont find a slot identifier field in the MPTS card properties.

The same of course applies to cards that are "autodetect and autoconfigure only" - in which case, if two dont work (but should), then ensure that all IRQ conflicts related to both are removed. On some occasions, one also also needs to go into the BIOS and select "Non Plug-and-Play OS" so that resource assignments are done - manually setting IRQs (where possible) is a good step as well.


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|