RU/2: Форум. Общение пользователей и разработчиков OS/2 (eCS). : Ответить на сообщение

Имя:
e-mail:
FIDO:
Home page:
сохранить данные о вас

Тема:

> Делаю, блин, за eCo его pаботу ;) Собиpает инфу пpо адаптеpы в unsupported, даже не пpиведя описания - чо делать ;)
> У меня пpицепить бpоадком 5787M получилось (вpоде, не только у меня).
> Пост найден где-то в дебpях GenMAC-mailing-list.
> Тока Netbeui в генмаке не pаботает, мpет на пеpвом же мегабайте. TCP/IP ноpмально.
> 
> -------------------------------------------------------------------------------
>      If  you look back through this lists archives, it's all already there from
> various people - but here's the combined text (thanks to the original authors -
> I am NOT one of them by the way): (I have already sent this to Herwig, Paul and
> Lewis, off-list.
> 
> Firstly some general guidance from Thorlof:
> 
>      Hi  all,  before  sending any request to support new hardware, PLEASE scan
> this  news-group  and  the available documentation (genmac.inf) what exactly is
> needed,  what  the user can check by himself (f.ex. unsupported mode) and if it
> makes  sense at all to support this card. We can't and won't support every card
> that  is  available on the windows-market, so PLEASE again check this newsgroup
> and  available OS/2-websites which cards are known working well with the driver
> and  get  exactly  that  model.  If a 32-bit Cardbus-card is not yet recognized
> correctly  by  OS/2,  it  makes  no  sense  to  get  a  driver  for it, because
> cbenable/pciconf often do not work on the system and thus the support of such a
> card  is  not possible at all! Some sources where to get informations: 
>  - GenMAC is maintained and distributed by netlabs.org: 
>    http://genmac.netlabs.org/ 
>  - If you need help for GenMAC itself please check the GenMAC-mailing-list at
>    Netlabs.org: http://news.gmane.org/gmane.org.netlabs.genmac.user/ 
>  - If you have problems with connecting to a WLAN, with TCP/IP-configuration, 
>    encryption etc. the WLAN-mailing-list might be the better place to search
>    and ask for: http://news.gmane.org/gmane.org.netlabs.wlan.general/ 
>  - Wireless LAN Monitor by Christian  Langanke (netlabs.org): 
>    http://wlan.netlabs.org/ 
>  - WPA Security with Wireless LAN Monitor by C. Langanke:
>    http://www.clanganke.de/os2/pres/wse2006/lan01/index.html    
>  - Craig Hart's PCI+AGP bus sniffer for OS/2 (compiled by Veit Kannegieser), 
>    up-to-date pcidevs.txt: http://kannegieser.net/veit/programm/pci104vka.arj
>    http://members.datafast.net.au/dft0802  
>  - Support for 32-bit CardBus-nics with OS/2 by Veit Kannegieser:
>    http://kannegieser.net/veit/test/pciconf_test.zip
>    http://kannegieser.net/veit/test/cbenable_test.zip  
>  - The presentation "LAN02: GenMAC 2.1 - current status" at WarpStock Europe 
>    2007: http://www.warpstock.eu/
>  - General hardware-compatibility-sites for OS/2: os2warp.be Compatible
>    Hardware List Web Site http://www.os2warp.be/ eComStation.RU - Hardware
>    http://en.ecomstation.ru/ 
> Thanks, -- Chau y hasta luego, Thorolf
> 
> Then how to enable "UNSUPPORTED" mode:
> Per E. Johannessen wrote: 
> > Hi, 
> >
> > Noticed that you have found your instructions, but thought I'd let you 
> > know that there is no need to edit the file genm32w.os2 any longer if
> > you are using genmac 2.1 or newer and the UNSUPPORTED option.
> >
> > Edit protocol.ini or use the mpts program to add UNSUPPORTED.
> > Below is my working PROTOCOL.INI
> > (DEBUGLEVEL = "ALL"....... is just for creating big log files)
> > Brgds,
> > Per
> > (Peter in English...) 
> >
> > [PROT_MAN]
> >
> > DRIVERNAME = PROTMAN$
> >
> > [IBMLXCFG]
> >
> > tcpip_nif = tcpip.nif
> > W8086X108C_nif = W8086x108C.nif
> >
> > [tcpip_nif]
> >
> > DriverName = TCPIP$
> > Bindings = W8086X108C_nif
> >
> > [W8086X108C_nif]
> >
> > DriverName = WRND32$
> > VENDOR = 0x8086
> > DEVICE = 0x108C
> > NDIS_SYS = "E1E5132.SYS"
> > NDIS_INF = "E1E5132.REG"
> > DEBUGLEVEL = "ALL"
> > OPTIONS = "UNSUPPORTED"
> >
> >
> > And finally all the other work that you need to do to NIF files, directories etc. 
> > I also found I needed to change the inf file baced on the Win XP registry 
> > settings: Having just got my 3C556 working with Genmav V2 and as Ed was asking 
> > in another thread, I thought I would document what I did. As ever USE AT YOUR 
> > OWN RISK and make a backup. 
>      1) Install genmac as per usual. 
>      2)  Scan the supported cards and find one that is a close match to yours -
> same  chipset for example or the known fact that XYZ also supports ABC on other
> platforms.
>      3)  cd  to  c:/ibmcom/macs. There will be a load of W*****.NIF files which
> are  inserted by Genmac install. The naming convention is W<pci vendor id>X<pci
> device  id>.NIF 
>      4)  Find  the  one for your chosen near match. Copy the near match to your
> new  name.  Open with your favourite editor and change the title - This is what
> appears  as the card description in MPTS - Change vendor and device IDs. Change
> the  windows  SYS and INF file names. Save the file. 
>      5)  open genm32w.os2 with a hex editor, starting around offset 5C40 is the
> list  of  supported  cards.  Search for your near match. Change the SYS and INF
> files  names  and descriptor as before. About 20 bytes *before* the description
> is the hex vendor and device IDs - Zap them to your new ones. Remember that PCs
> have  byte  order  reversed. So in my case, 10B7 6056 I zapped it to B710 5660.
> Save  the  file.  
>      6)  cd  to  c:/genmac/driver. Create a directory WRAPPER_<pci vendor>_<pci
> device> into this directory you just created copy the Win .SYS & .INF files. 
>      7)  Reboot  and  see  what  happens.  Genmac  writes  a  log of sorts into
> c:genmacdriver  as  WRND32.LOG.  Also  c:/ibmcom/lantran.log  may  yeild some
> clues.  Notes.  Now the two bytes after the vendor/device in genm32w.os2 appear
> to  be  flag  bits - but of course we don't know what they mean and I very much
> doubt  that  anyone  is  going to tell us :-) The "no hardware in protocol.ini"
> message basically means it can't find the device/vendor id specified. Which was
> what I was getting with all the above done except the hex vendor/device zap. It
> would  be nice to know the debug switches for Genmac, but again I doubt we will
> be  told  - Because of course we are all to stupid to understand. Hope it helps
> someone. -- Regards Dave Saville
> 
> R. M. Klippstein wrote:
> 
>      Having  instructions  posted  as to how to implement "Unsupported Mode" is
> something  virtually all of use would like to see. Is this information only for
> a  few  selected  people to receive via a E-Mail? Of all the people involved in
> eCS/OS2  Herwig  would  use  this information to all of our advantage as he and
> Paul  have  done in the past. Could some kind soul outline for all of us how to
> use this feature?

_, _, _, _, _ _ _,_ (_ \| / \ \|\ \| \| \|_/ , ) \| , \ / \| \\| \| \| \ ~ ~~~ ~ ~ ~ ~ ~ ~