Date: Sat, 6 Mar 2004 00:04:02 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 306 ************************************************** Friday 05 March 2004 Number 306 ************************************************** Subjects for today 1 tar & at LongLink : John Poltorak 2 Re: tar & at LongLink : Thomas Dickey 3 Re: tar & at LongLink : Thomas Dickey 4 Re: tar & at LongLink : John Poltorak 5 Re: tar & at LongLink : Thomas Dickey 6 Re: tar & at LongLink : John Poltorak 7 Re: tar & at LongLink : Thomas Dickey 8 Re: tar & at LongLink : John Poltorak 9 Re: tar & at LongLink : Thomas Dickey 10 Re: tar & at LongLink : Henry Sobotka 11 Re: tar & at LongLink : Thomas Dickey 12 Re: tar & at LongLink : Thomas Dickey 13 Re: tar & at LongLink : Lyn St George" **= Email 1 ==========================** Date: Thu, 4 Mar 2004 17:10:59 +0000 From: John Poltorak Subject: tar & at LongLink It appears that tar (GTAK) is unable to extract files with a long embedded directory name and when it comes across such files, it displays .././ at LongLink How can can you set about extracting files like this from archives? -- John **= Email 2 ==========================** Date: Thu, 4 Mar 2004 12:19:48 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Thu, 4 Mar 2004, John Poltorak wrote: > > > It appears that tar (GTAK) is unable to extract files with a long embedded > directory name and when it comes across such files, it displays > ././ at LongLink > > How can can you set about extracting files like this from archives? gtak is rather old (at least the version I've seen). A more recent port of GNU tar would presumably handle this (since it's GNU-tar-specific). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 3 ==========================** Date: Thu, 4 Mar 2004 12:19:48 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Thu, 4 Mar 2004, John Poltorak wrote: > > > It appears that tar (GTAK) is unable to extract files with a long embedded > directory name and when it comes across such files, it displays > ././ at LongLink > > How can can you set about extracting files like this from archives? gtak is rather old (at least the version I've seen). A more recent port of GNU tar would presumably handle this (since it's GNU-tar-specific). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 4 ==========================** Date: Thu, 4 Mar 2004 17:38:03 +0000 From: John Poltorak Subject: Re: tar & at LongLink On Thu, Mar 04, 2004 at 12:19:48PM -0500, Thomas Dickey wrote: > On Thu, 4 Mar 2004, John Poltorak wrote: > > > > > > > It appears that tar (GTAK) is unable to extract files with a long embedded > > directory name and when it comes across such files, it displays > > ././ at LongLink > > > > How can can you set about extracting files like this from archives? > > gtak is rather old (at least the version I've seen). A more recent port > of GNU tar would presumably handle this (since it's GNU-tar-specific). The port of tar 1.10 by Andreas Kaiser is the only one I am aware of. Unfortunately no one has been able to track down the source for that so it makes bringing tar uptodate quite tricky. > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 5 ==========================** Date: Thu, 4 Mar 2004 17:29:51 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Thu, 4 Mar 2004, John Poltorak wrote: > On Thu, Mar 04, 2004 at 12:19:48PM -0500, Thomas Dickey wrote: > > On Thu, 4 Mar 2004, John Poltorak wrote: > > > > > > > > > > > It appears that tar (GTAK) is unable to extract files with a long embedded > > > directory name and when it comes across such files, it displays > > > ././ at LongLink > > > > > > How can can you set about extracting files like this from archives? > > > > gtak is rather old (at least the version I've seen). A more recent port > > of GNU tar would presumably handle this (since it's GNU-tar-specific). > > The port of tar 1.10 by Andreas Kaiser is the only one I am aware of. I believe that's too old. 1.12 would probably be a good target for porting - I haven't found much time for OS/2 recently (didn't get anywhere getting the network card on my newest computer to work with ECS, so I've only the older EMX stuff for ports). > Unfortunately no one has been able to track down the source for that so it > makes bringing tar uptodate quite tricky. > > > > -- > > Thomas E. Dickey > > http://invisible-island.net > > ftp://invisible-island.net > > > -- > John > > > > -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 6 ==========================** Date: Thu, 4 Mar 2004 22:51:13 +0000 From: John Poltorak Subject: Re: tar & at LongLink On Thu, Mar 04, 2004 at 05:29:51PM -0500, Thomas Dickey wrote: > 1.12 would probably be a good target for porting - I haven't found much > time for OS/2 recently (didn't get anywhere getting the network card on > my newest computer to work with ECS, so I've only the older EMX stuff for > ports). Which NIC is it? I'm sure we can get you networked without too much trouble. > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 7 ==========================** Date: Thu, 4 Mar 2004 18:13:21 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Thu, 4 Mar 2004, John Poltorak wrote: > On Thu, Mar 04, 2004 at 05:29:51PM -0500, Thomas Dickey wrote: > > > 1.12 would probably be a good target for porting - I haven't found much > > time for OS/2 recently (didn't get anywhere getting the network card on > > my newest computer to work with ECS, so I've only the older EMX stuff for > > ports). > > Which NIC is it? > > I'm sure we can get you networked without too much trouble. It's an on-board SIS900. I found a driver for it, but something isn't right. Here's what Linux identifies for it: sis900.c: v1.08.06 9/24/2002 eth0: Realtek RTL8201 PHY transceiver found at address 2. eth0: Using transceiver found at address 2 as default eth0: SiS 900 PCI Fast Ethernet at 0xd800, IRQ 11, 00:40:ca:58:80:1c. and ibmcom/lantran.log, which seems to have comparable information (the only interesting text-file from the last time I booted ECS): LT00073: FFST/2 is installed but is not started. LANTRAN.LOG is being created. IBM OS/2 LANMSGDD [08/01/02] 6.00 is loaded and operational. IBM - OS/2 Socket/MPTS Common Transport Semantics IBM OS/2 NETBEUI 6.00.0 NETBEUI: Using a 32-bit data segment. IBM OS/2 TCPBEUI 6.00.0 TCPBEUI: Using a 32-bit data segment. Installing NETWKSTA.200 Version 6.0. IBM LAN Redirector ( May 21, 2002) IBM OS/2 NETBIOS 4.0 Adapter 0 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS applications. Adapter 1 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS applications. NETBIOS 4.0 is loaded and operational. IBM LANVDD is loaded and operational. IBM OS/2 LAN Netbind PRO0030: Multiple adapters are trying to use the same interrupt level. The request to bind VECTOR to SIS900_NIF cannot be completed. IBM - OS/2 Socket/MPTS NetBios Service Driver TCPBEUI: Logical adapter 0 is trying to bind to TCP/IP interface lan0. LT00141: Errors occurred while attempting to initialize TCPBEUI. I put a copy of my config.sys in ftp://invisible-island.net/temp/my-config.zip For other information I'll have to reboot & poke around. If I had the network card working, I'd be doing more with it - but getting development data on/off would be painful (floppies ;-). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 8 ==========================** Date: Thu, 4 Mar 2004 23:25:44 +0000 From: John Poltorak Subject: Re: tar & at LongLink On Thu, Mar 04, 2004 at 06:13:21PM -0500, Thomas Dickey wrote: > On Thu, 4 Mar 2004, John Poltorak wrote: > > > On Thu, Mar 04, 2004 at 05:29:51PM -0500, Thomas Dickey wrote: > > > > > 1.12 would probably be a good target for porting - I haven't found much > > > time for OS/2 recently (didn't get anywhere getting the network card on > > > my newest computer to work with ECS, so I've only the older EMX stuff for > > > ports). > > > > Which NIC is it? > > > > I'm sure we can get you networked without too much trouble. > > It's an on-board SIS900. I found a driver for it, but something isn't > right. Here's what Linux identifies for it: > > sis900.c: v1.08.06 9/24/2002 > eth0: Realtek RTL8201 PHY transceiver found at address 2. > eth0: Using transceiver found at address 2 as default > eth0: SiS 900 PCI Fast Ethernet at 0xd800, IRQ 11, 00:40:ca:58:80:1c. > > and ibmcom/lantran.log, which seems to have comparable information (the > only interesting text-file from the last time I booted ECS): > > NETBEUI: Using a 32-bit data segment. > IBM OS/2 TCPBEUI 6.00.0 > TCPBEUI: Using a 32-bit data segment. I normally install NETBIOS and TCP/IP as seperate protocols. I've heard of people having problems getting TCPBEUI working.... Straight TCP/IP should work without much difficulty. Maybe post your PROTOCOL.INI... > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net -- John **= Email 9 ==========================** Date: Thu, 4 Mar 2004 21:00:40 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Thu, 4 Mar 2004, John Poltorak wrote: > On Thu, Mar 04, 2004 at 06:13:21PM -0500, Thomas Dickey wrote: > > On Thu, 4 Mar 2004, John Poltorak wrote: > > > > > On Thu, Mar 04, 2004 at 05:29:51PM -0500, Thomas Dickey wrote: > > > > > > > 1.12 would probably be a good target for porting - I haven't found much > > > > time for OS/2 recently (didn't get anywhere getting the network card on > > > > my newest computer to work with ECS, so I've only the older EMX stuff for > > > > ports). > > > > > > Which NIC is it? > > > > > > I'm sure we can get you networked without too much trouble. > > > > It's an on-board SIS900. I found a driver for it, but something isn't > > right. Here's what Linux identifies for it: > > > > sis900.c: v1.08.06 9/24/2002 > > eth0: Realtek RTL8201 PHY transceiver found at address 2. > > eth0: Using transceiver found at address 2 as default > > eth0: SiS 900 PCI Fast Ethernet at 0xd800, IRQ 11, 00:40:ca:58:80:1c. > > > > and ibmcom/lantran.log, which seems to have comparable information (the > > only interesting text-file from the last time I booted ECS): > > > > NETBEUI: Using a 32-bit data segment. > > IBM OS/2 TCPBEUI 6.00.0 > > TCPBEUI: Using a 32-bit data segment. > > I normally install NETBIOS and TCP/IP as seperate protocols. It's been a few months since I was into the configuration dialogs - I only recall that I tried several combinations without seeing any improvement. (The online help-messages weren't helpful ;-) > I've heard of people having problems getting TCPBEUI working.... Straight > TCP/IP should work without much difficulty. > > Maybe post your PROTOCOL.INI... ftp://invisible-island.net/temp/my-protocol.zip (thanks) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 10 ==========================** Date: Thu, 04 Mar 2004 22:12:39 -0500 From: Henry Sobotka Subject: Re: tar & at LongLink Thomas Dickey wrote: > > PRO0030: Multiple adapters are trying to use the same interrupt level. [C:\]help PRO0030 PRO0030: Multiple adapters are trying to use the same interrupt level. The request to bind *** to *** cannot be completed. Cause: Multiple adapters have been set to use the same interrupt level when 1 or more adapters do not share interrupts, causing an unrecoverable conflict. Action: Run the hardware diagnostics for the adapters and correct the interrupt conflict. 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. h~ -- Free software, free minds. **= Email 11 ==========================** Date: Fri, 5 Mar 2004 05:10:26 -0500 (EST) From: Thomas Dickey Subject: Re: tar & at LongLink On Thu, 4 Mar 2004, John Poltorak wrote: > > NETBEUI: Using a 32-bit data segment. > > IBM OS/2 TCPBEUI 6.00.0 > > TCPBEUI: Using a 32-bit data segment. > > I normally install NETBIOS and TCP/IP as seperate protocols. I recall some install-dialog for selecting protocols, but don't want to go back to the install (each time I did that, I had to reinstall 2-3 other operating systems since they have different ideas about booting ;-). > I've heard of people having problems getting TCPBEUI working.... Straight > TCP/IP should work without much difficulty. > > Maybe post your PROTOCOL.INI... Looking at the one from the older machine, I see they both have a section for TCPBEUI_NIF which looks "similar". But the newer one has a NETBIOS section with two adapters listed where the other does not, e.g., (new) [NETBIOS] DRIVERNAME = NETBIOS$ ADAPTER0 = TCPBEUI$,0 ADAPTER1 = NETBEUI$,1 (old) [NETBIOS] DriverName = NETBIOS$ ADAPTER1 = TCPBEUI$,1 and similar names appear in the respective IBMLXCFG sections. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 12 ==========================** Date: Fri, 5 Mar 2004 05:38:39 -0500 (EST) From: Thomas Dickey 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 **= Email 13 ==========================** Date: Fri, 05 Mar 2004 11:03:42 +0000 From: "Lyn St George" Subject: Re: tar & at LongLink On Fri, 5 Mar 2004 05:10:26 -0500 (EST), Thomas Dickey wrote: >[NETBIOS] > > DRIVERNAME = NETBIOS$ > ADAPTER0 = TCPBEUI$,0 > ADAPTER1 = NETBEUI$,1 > >(old) > >[NETBIOS] > > DriverName = NETBIOS$ > ADAPTER1 = TCPBEUI$,1 I've missed part of this thread, but I recall a similar thing happening to me. Commenting out ADAPTOR1 should fix it (the first one is '0', not '1') - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting +----------------------------------------------------------------------------------