Date: Sun, 7 Mar 2004 00:04:04 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 307 ************************************************** Saturday 06 March 2004 Number 307 ************************************************** Subjects for today 1 Re: tar & at LongLink : jimburke200 at earthlink.net (James E. Burke Jr.) 2 Re: tar & at LongLink : Christian Hennecke" 3 Re: tar & at LongLink : John Poltorak 4 Re: tar & at LongLink : Thomas Dickey 5 Re: tar & at LongLink : John Poltorak 6 Re: tar & at LongLink : Thomas Dickey 7 Re: tar & at LongLink : Christian Hennecke" 8 Re: tar & at LongLink : Thomas Dickey 9 Re: tar & at LongLink : John Poltorak 10 Re: tar & at LongLink : Thomas Dickey 11 Re: tar & at LongLink : John Poltorak 12 Re: tar & at LongLink : Thomas Dickey **= Email 1 ==========================** Date: Fri, 05 Mar 2004 05:32:35 -0800 From: jimburke200 at earthlink.net (James E. Burke Jr.) Subject: Re: tar & at LongLink >On Thu, 4 Mar 2004, Henry Sobotka wrote: > >> Judging from the Linux output, IRQ 11 is likely the interrupt involved. >> Hardware Manager should tell you what other adapter is using it and >> either one might have a mechanism such as a load parameter for changing >> it. There's also a utility on Hobbes for changing IRQ settings for PCI >> devices, if that's what they are. A search for IRQ or PCI should turn it >> up. > >Yes - I see that. I'm thinking that the problem is that I've got the >same adapter installed twice, and am not sure how to fix that through >the dialogs. (Simply editing protocol.ini has occurred to me but I'm >not sure if that's a good idea). > >-- >Thomas E. Dickey >http://invisible-island.net >ftp://invisible-island.net The lantran.log tells you it is an irq conflict. The two instances of netbios are not a problem since one is a logical adapter for netbeui (1) and the other is for tcpbeui (0). You need to go to chuck McKinnis' pages and verify that this adapter is supported and that you have the correct nif files for it and see which device is sharing the irq. There might even be a dos program that you can use to change the irq or there might be a setting when you run mpts.exe and configure the adapter. If you still have problems, I'd suggest you post them to the ecomstation.support.networking newsgroup where I'm sure someone who has that adapter can tell you how they got it working. **= Email 2 ==========================** Date: Fri, 05 Mar 2004 20:27:56 +0100 (CET) From: "Christian Hennecke" Subject: Re: tar & at LongLink On Fri, 5 Mar 2004 05:38:39 -0500 (EST), Thomas Dickey wrote: >> Judging from the Linux output, IRQ 11 is likely the interrupt involved. >> Hardware Manager should tell you what other adapter is using it and >> either one might have a mechanism such as a load parameter for changing >> it. There's also a utility on Hobbes for changing IRQ settings for PCI >> devices, if that's what they are. A search for IRQ or PCI should turn it >> up. > >Yes - I see that. I'm thinking that the problem is that I've got the >same adapter installed twice, and am not sure how to fix that through >the dialogs. (Simply editing protocol.ini has occurred to me but I'm >not sure if that's a good idea). When you edit the NIC driver properties via MPTS, you can usually specify the device or PCI bus id. Christian Hennecke **= Email 3 ==========================** Date: Fri, 5 Mar 2004 19:38:12 +0000 From: John Poltorak Subject: Re: tar & at LongLink On Fri, Mar 05, 2004 at 05:38:39AM -0500, Thomas Dickey wrote: > On Thu, 4 Mar 2004, Henry Sobotka wrote: > > > Judging from the Linux output, IRQ 11 is likely the interrupt involved. > > Hardware Manager should tell you what other adapter is using it and > > either one might have a mechanism such as a load parameter for changing > > it. There's also a utility on Hobbes for changing IRQ settings for PCI > > devices, if that's what they are. A search for IRQ or PCI should turn it > > up. > > Yes - I see that. I'm thinking that the problem is that I've got the > same adapter installed twice, and am not sure how to fix that through > the dialogs. (Simply editing protocol.ini has occurred to me but I'm > not sure if that's a good idea). There's no problem editing protocol.ini - just save a copy of it, in case you mess it up completely, but I guess that doesn't matter since it doesn't work anyway. MPTS is simply a GUI frontend for creating/editing it. It would be nice to have a dialog version ;-)... Any changes do not take effect until after a reboot. > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 4 ==========================** Date: Fri, 5 Mar 2004 15:10:23 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Fri, 5 Mar 2004, John Poltorak wrote: > On Fri, Mar 05, 2004 at 05:38:39AM -0500, Thomas Dickey wrote: > > On Thu, 4 Mar 2004, Henry Sobotka wrote: > > > > > Judging from the Linux output, IRQ 11 is likely the interrupt involved. > > > Hardware Manager should tell you what other adapter is using it and > > > either one might have a mechanism such as a load parameter for changing > > > it. There's also a utility on Hobbes for changing IRQ settings for PCI > > > devices, if that's what they are. A search for IRQ or PCI should turn it > > > up. > > > > Yes - I see that. I'm thinking that the problem is that I've got the > > same adapter installed twice, and am not sure how to fix that through > > the dialogs. (Simply editing protocol.ini has occurred to me but I'm > > not sure if that's a good idea). > > There's no problem editing protocol.ini - just save a copy of it, in case > you mess it up completely, but I guess that doesn't matter since it > doesn't work anyway. I do that from habit (don't like to make my machine unusable ;-). Actually what I had in mind was having noticed that some of the settings appear to be saved in binary form (though - poking around in the directory tree I don't see any examples). Some things do complicate it. I started this box in an alternate location with a 17" monitor and when it was stable, put it on the 19" monitor. Now that I'm reminded, ECS had trouble recognizing the monitor, so I had to tinker a little to get the display back. (That was in September - time goes rapidly). > MPTS is simply a GUI frontend for creating/editing it. > It would be nice to have a dialog version ;-)... perhaps (but I'm mainly interested in things at a lower level, such as making dialog work nicely). > Any changes do not take effect until after a reboot. I sort of assumed that - all of the action takes place during startup. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 5 ==========================** Date: Fri, 5 Mar 2004 20:32:15 +0000 From: John Poltorak Subject: Re: tar & at LongLink On Fri, Mar 05, 2004 at 03:10:23PM -0500, Thomas Dickey wrote: > > There's no problem editing protocol.ini - just save a copy of it, in case > > you mess it up completely, but I guess that doesn't matter since it > > doesn't work anyway. > > I do that from habit (don't like to make my machine unusable ;-). > Actually what I had in mind was having noticed that some of the settings > appear to be saved in binary form (though - poking around in the directory > tree I don't see any examples). The networking stuff doesn't include any binary config files, AFAIK. > Some things do complicate it. I started this box in an alternate location > with a 17" monitor and when it was stable, put it on the 19" monitor. Now > that I'm reminded, ECS had trouble recognizing the monitor, so I had to > tinker a little to get the display back. Monitors and screen resolution are a different ball game with some of the settings being held in the OS2.INI file. If you ever mess up the display, you need to go to a command prompt and run SETVGA, then start again. > (That was in September - time goes rapidly). Sure does! > > MPTS is simply a GUI frontend for creating/editing it. > > It would be nice to have a dialog version ;-)... > > perhaps (but I'm mainly interested in things at a lower level, such as > making dialog work nicely). I'm not really sure about the ins and outs of it, but once you have selected your NIC, the corresponding MACS\*nic*.nif file is processed and certain bits of it get copied to the protocol.ini being written. The same goes for PROTOCOL\*.nif after you select which protocol(s) you want to bind to the selected NIC. I wish I knew more about it myself. > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 6 ==========================** Date: Fri, 5 Mar 2004 18:35:41 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Fri, 5 Mar 2004, John Poltorak wrote: > I'm not really sure about the ins and outs of it, but once you have > selected your NIC, the corresponding MACS\*nic*.nif file is processed and > certain bits of it get copied to the protocol.ini being written. The same > goes for PROTOCOL\*.nif after you select which protocol(s) you want to > bind to the selected NIC. I wish I knew more about it myself. thanks to the feedback (I'd forgotten some parts such as rmview), I'm able to get the network up. The driver that's conflicting (assigned to IRQ 11 according to hardware manager) is USBOHCD.SYS (I've two lines for that in config.sys). I commented them out to see if that improved things, and am connected on the net now. So I'll have to read and see what those drivers are for, and how to set the IRQ so it's not conflicting. Between scanpci and rmview, it looks as if I'm not using IRQ 10. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 7 ==========================** Date: Sat, 06 Mar 2004 01:50:24 +0100 (CET) From: "Christian Hennecke" Subject: Re: tar & at LongLink On Fri, 5 Mar 2004 18:35:41 -0500 (EST), Thomas Dickey wrote: >> I'm not really sure about the ins and outs of it, but once you have >> selected your NIC, the corresponding MACS\*nic*.nif file is processed and >> certain bits of it get copied to the protocol.ini being written. The same >> goes for PROTOCOL\*.nif after you select which protocol(s) you want to >> bind to the selected NIC. I wish I knew more about it myself. > >thanks to the feedback (I'd forgotten some parts such as rmview), I'm able >to get the network up. The driver that's conflicting (assigned to IRQ 11 >according to hardware manager) is USBOHCD.SYS (I've two lines for that in >config.sys). That's the USB base support driver for OHCI USB controllers. It looks like other drivers in your system are not capable of sharing IRQs the correct way. This, unfortunately, is not uncommon with a number of OS/2 drivers for sound cards, NICs, and SCSI controllers. Christian Hennecke **= Email 8 ==========================** Date: Fri, 5 Mar 2004 20:08:25 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Sat, 6 Mar 2004, Christian Hennecke wrote: > On Fri, 5 Mar 2004 18:35:41 -0500 (EST), Thomas Dickey wrote: > >to get the network up. The driver that's conflicting (assigned to IRQ 11 > >according to hardware manager) is USBOHCD.SYS (I've two lines for that in > >config.sys). > > That's the USB base support driver for OHCI USB controllers. It looks > like other drivers in your system are not capable of sharing IRQs the > correct way. This, unfortunately, is not uncommon with a number of OS/2 > drivers for sound cards, NICs, and SCSI controllers. That's about what I could find with google. The only device I've got on the USB is a zipdrive, and I don't think OS/2 recognized that (it's not important anyway in this context). The network driver is necessary to let me move files on/off the development. (I'd copy files to a vfat partition, but ECS didn't recognize that either). Also of course, for testing tin & lynx. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 9 ==========================** Date: Sat, 6 Mar 2004 11:40:26 +0000 From: John Poltorak Subject: Re: tar & at LongLink On Fri, Mar 05, 2004 at 08:08:25PM -0500, Thomas Dickey wrote: > That's about what I could find with google. The only device I've got on > the USB is a zipdrive, and I don't think OS/2 recognized that (it's not > important anyway in this context). The network driver is necessary to let > me move files on/off the development. (I'd copy files to a vfat > partition, but ECS didn't recognize that either). You should be able to access a VFAT partition. Do you have FAT32.IFS installed and if so which version? > Also of course, for testing tin & lynx. Any news on tin & lynx ? Incidentally, I'm aware of problems with people trying to download BYACC from time to time. Is your system always available? BYACC is a key component in UX2BS because a number of builds of various apps are dependent on it. If BYACC can't be retrieved then the build of those apps fails. > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 10 ==========================** Date: Sat, 6 Mar 2004 06:53:12 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Sat, 6 Mar 2004, John Poltorak wrote: > On Fri, Mar 05, 2004 at 08:08:25PM -0500, Thomas Dickey wrote: > > > That's about what I could find with google. The only device I've got on > > the USB is a zipdrive, and I don't think OS/2 recognized that (it's not > > important anyway in this context). The network driver is necessary to let > > me move files on/off the development. (I'd copy files to a vfat > > partition, but ECS didn't recognize that either). > > You should be able to access a VFAT partition. Do you have FAT32.IFS > installed and if so which version? It's not in my config.sys > > Also of course, for testing tin & lynx. > > Any news on tin & lynx ? not much. I did test compile/run lynx shortly before the 2.8.5 release (same with ncurses). So they should work. > Incidentally, I'm aware of problems with people trying to download BYACC > from time to time. Is your system always available? BYACC is a key I get occasional comments about this, but not enough to look for another ISP. > component in UX2BS because a number of builds of various apps are > dependent on it. If BYACC can't be retrieved then the build of those apps > fails. > > > > -- > > Thomas E. Dickey > > http://invisible-island.net > > ftp://invisible-island.net > > > -- > John > > > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 11 ==========================** Date: Sat, 6 Mar 2004 12:03:11 +0000 From: John Poltorak Subject: Re: tar & at LongLink On Sat, Mar 06, 2004 at 06:53:12AM -0500, Thomas Dickey wrote: > On Sat, 6 Mar 2004, John Poltorak wrote: > > > You should be able to access a VFAT partition. Do you have FAT32.IFS > > installed and if so which version? > > It's not in my config.sys I'm not sure how you would expect to access it without a driver... Maybe check this:- http://www.os2.cz/news2085.html > > > Also of course, for testing tin & lynx. > > > > Any news on tin & lynx ? > > not much. I did test compile/run lynx shortly before the 2.8.5 > release (same with ncurses). So they should work. Is 2.8.5 the latest release? How about tin? Any chance of the definitive URLs for both? > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 12 ==========================** Date: Sat, 6 Mar 2004 07:19:31 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Sat, 6 Mar 2004, John Poltorak wrote: > On Sat, Mar 06, 2004 at 06:53:12AM -0500, Thomas Dickey wrote: > > On Sat, 6 Mar 2004, John Poltorak wrote: > > > > > You should be able to access a VFAT partition. Do you have FAT32.IFS > > > installed and if so which version? > > > > It's not in my config.sys > > I'm not sure how you would expect to access it without a driver... ( I wouldn't ;-) > > Maybe check this:- > > > http://www.os2.cz/news2085.html ok (will try that) > > > > > Also of course, for testing tin & lynx. > > > > > > Any news on tin & lynx ? > > > > not much. I did test compile/run lynx shortly before the 2.8.5 > > release (same with ncurses). So they should work. > > Is 2.8.5 the latest release? yes > How about tin? 1.7.4 > Any chance of the definitive URLs for both? http://lynx.isc.org http://www.tin.org -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net