Adding network and internet to Warp 4
Snydley
it "found" my NIC card, and loaded the generic Realtek OS/2 driver for it
that I have, but I can't figure out how to set it up to get on the Internet.
Also during the install it "found" my Sounblaster AWE32 PnP and loaded it's
drivers for it. That never worked right though. I finally got so frustrated
with it I fdisked the drive and started over. I ended up doing this several
times. During the last install the sound works,(except for some
"clicking",(think it's a DMA problem), but it didn't load my NIC card and I
can't figure out how to add it, LAN capabilities and TCP/IP. I saw on one of
the earlier installs there was a TCP/IP install program, or configuration
program, but this time it's missing. I found the area where you can add
programs and added "ALL" hoping it would show up, but it didn't.
Can anyone give me a clue as to where to start to add Network and Internet
capabilities, and how to configure hardware settings,(like Device Mangler)
in Windows.
On another note, On this system I have removable hard drives that are on
"drawers" that I can change and run whatever software I want on it without
opening the machine and removing the hard drive.
On one of the hard drives I have Windows 98SE, and when I'm using that hard
drive on the system the Sounblaster and NIC card works perfectly, I get
sound with Windows and all of my apps. and can connect to 3 other computers
on the LAN and also surf the Net, so I know my hardware is ok.
I appreciate any help you can give, with suggestions, websites etc.
Thanks,
Snyde
William L. Hartzell
Snydley wrote:
> I'm set up Warp 4 on an old Pentium 233Mhz MMX computer. During the install
> it "found" my NIC card, and loaded the generic Realtek OS/2 driver for it
> that I have, but I can't figure out how to set it up to get on the Internet.
You should note that there are more than one driver for RealTek NIC.
I'd suggest get the others and trying them in turn, until you get a good
setup(check the lantrans.log file in \IBMCOM folder for success). Try
Hobbes for these other drivers. BTW, use
<http://hobbes.nmsu.edu/pub/os2/util/misc/pci104vka.zip> to find out
which Realtek chip driver you need.
> Also during the install it "found" my Sounblaster AWE32 PnP and loaded it's
> drivers for it. That never worked right though.
Alas, the IBM compiled drivers have never worked right.
<http://hobbes.nmsu.edu/pub/os2/system/drivers/sound/soundblasterawe3264_latest.zip>
I finally got so frustrated
> with it I fdisked the drive and started over. I ended up doing this several
> times. During the last install the sound works,(except for some
> "clicking",(think it's a DMA problem), but it didn't load my NIC card and I
> can't figure out how to add it, LAN capabilities and TCP/IP. I saw on one of
> the earlier installs there was a TCP/IP install program, or configuration
> program, but this time it's missing. I found the area where you can add
> programs and added "ALL" hoping it would show up, but it didn't.
> Can anyone give me a clue as to where to start to add Network and Internet
> capabilities, and how to configure hardware settings,(like Device Mangler)
> in Windows.
> On another note, On this system I have removable hard drives that are on
> "drawers" that I can change and run whatever software I want on it without
> opening the machine and removing the hard drive.
> On one of the hard drives I have Windows 98SE, and when I'm using that hard
> drive on the system the Sounblaster and NIC card works perfectly, I get
> sound with Windows and all of my apps. and can connect to 3 other computers
> on the LAN and also surf the Net, so I know my hardware is ok.
> I appreciate any help you can give, with suggestions, websites etc.
> Thanks,
> Snyde
>
>
On Warp 4 CD Rom install disk, enter the install command to install
Networking applications after you get the right NIC driver. BTW you
need to get fixpack 15 for the base operating system
<http://hobbes.nmsu.edu/pub/os2/system/patches/fixpack/warp_4/fp15.zip>,
updated everything. Sad that Rick Oliver sites is gone as he had
pointers to all that you need to do. This site has drivers if you don't
find them on Hobbes <http://os2site.com/sw/>. Explorer it.
--
Bill
Thanks a Million!
Snydley
Sir? I'm not a Knight, but thanks just the same. :-)
I've resurrected this old Pentium to run all my old apps and games on and I
found a copy of Warp 4,, new in box, on sale on eBay. I never ran Os/2 when
it was first released, so I thought I'd try it this time. Hopefully it'll
run all my software. If not, I'll create another partition on the disk and
install DOS and maybe Winblows for those programs. :-)
Thanks for the help, I'm in the dark here, and will probably be calling for
more help as time goes on with this.
Take care,
Snyde
"William L. Hartzell" <wlhar...@tx.rr.com> wrote in message
news:48587a81$0$27969$4c36...@roadrunner.com...
jch
> I've resurrected this old Pentium to run all my old apps and games on and I
> found a copy of Warp 4,, new in box, on sale on eBay. I never ran Os/2 when
> it was first released, so I thought I'd try it this time. Hopefully it'll
> run all my software. If not, I'll create another partition on the disk and
> install DOS and maybe Winblows for those programs. :-)
> Thanks for the help, I'm in the dark here, and will probably be calling for
> more help as time goes on with this.
_____
A little while ago i reported a problem with a Warp 4 installation on a
large hard disk (8 Gb). Turns out that even after modifying the
installation floppies to allow for large disks, one has to make sure
that the installation partition does not exceed 2 Gb. If it does, the
installation program fails to install the networking code. After i
reduced the installable partition to 2 Gb, everything installed perfectly.
--
Regards / JCH
Pete
With v 4.5x, if you're trying to install peer, it's best done along with
the system installation. If you try to do it afterwards, check your
config.sys file and temporarily shorten any line which exceeds 254
characters. Install peer, then "repair" all the lines you had to shorten
in config.sys. This is a bug, which I believe has been fixed either by
the time fp15 was releaseed or with ecs.
HTH,
Pete
--
Jack Wise
Warp 4 will fit easily on 250 MB (yes Megabytes!). Even with Warp
Server! My "C" drive is only 250 MB and holds only the Operating
System. All programs are installed on other drives/partitions.
That way I can back up / Restore only the Operating System and never
affect any other programs or data.
--
Jack Wise
TEXAS red wine: renowned for its smoky-mesquite-bbq & jalapeno
overtones, the perfect foil for a meal of tacos and refried beans...
Snydley
Told you I'd probably be back. :-)
See the text below.
"William L. Hartzell" <wlhar...@tx.rr.com> wrote in message
news:48587a81$0$27969$4c36...@roadrunner.com...
I downloaded the files from the links you gave me. The SoundBlaster one
works great! The sound is wonderful now. I tried one of the other drivers
from Hobbes that was supposedly for my D-link DFE-530TX+ NIC and when the
machine restarted after the change I saw a "FATAL No such card in system" or
something similar. So I edited Config.sys manually from a command prompt
using "e" and removed the reference to that driver. Is there a way to do
that with a program in OS/2, something like Device Manager in Windows? I
then fdisked the drive and reinstalled, because I don't know how to add or
remove a NIC card and drivers from OS/2. How do you do that? This time when
I reinstalled, and it prompted me to choose a NIC card I selected "Other"
and installed the original Realtek driver I told you about. I checked the
lantran.log file with "e" and this is what it says:
IBM OS/2 LANMSGDD [08/01/96] 5.05 is loaded and operational.
IBM OS/2 NETBEUI 5.00.0
NETBEUI: Using a 32-bit data segment.
Installing NETWKSTA.200 Version 5.0. IBM LAN Redirector (Aug 15, 1996)
IBM OS/2 NETBIOS 4.0
Adapter 0 has 105 NCBs, 154 sessions, and 14 names available to NETBIOS
applications.
NETBIOS 4.0 is loaded and operational.
Loading Realtek Fast Ethernet Network Adapter driver (3.23vk) [2005-12-05]
Vendor=1186,1186 Dev.=1300,1301 Bus/Dev/Func-No= 0/10/0
EtherID=@00055DD05F50
The chip is RTL8139C.
Network Line Speed is 100 Mbps / Full-Duplex Mode.
Link configuration: Auto Negotiation enabled.
Flow Control: Transmit:Disabled, Receive:Disabled.
Parameters: IOBase = 0x7C00
Interrupt Level = 3
IBM LANVDD is loaded and operational.
IBM OS/2 LAN Netbind
To me it looks like it's working ok, but I've never gotten that "deep" into
Networks,(Windows always handled that), so I'm not sure. The only
questionable thing I see is the flow control. Should that be enabled, or is
this the way it should be?
I've got everything working, that I can tell, except the Network and
Internet. I did have 2 errors in Config.sys a "com.sys" and a "vcom.sys"not
loading . I was wondering if maybe that was caused by me selecting Fax
service during the install, but not having a fax-modem, so I manually rem'd
those 2 lines out in config.sys and those errors went away.
This computer is connected to 3 other computers on a network and the
Internet through a Netgear router. When I have the Windows'98SE hard drive
in the hard drive "drawer" I can connect to any of the 3 computers and swap
files and use a printer connected to one of them, and surf the Net, so I'm
sure my hardware's ok.
I think my whole problem now with the network is I just don't know how to
set it up. The only experience I've had with networks is with Windows and it
takes care of all of this for you, pretty much.
Is there anywhere on the Net where I can find a webpage with step by step
directions, or some kind of guide or something? This seems to be the last
problem I have with the setup, and I'd appreciate any help you might give
me.
Thanks,
Snyde
Andrew Stephenson
jw...@hal-pc.org "Jack Wise" writes:
> Jack Wise
>
> TEXAS red wine: renowned for its smoky-mesquite-bbq & jalapeno
> overtones, the perfect foil for a meal of tacos and refried beans...
I thort them Texicanos didn't hold with reds, nowhow -- exceptin'
them as is properly dead.
--
Andrew Stephenson
Jack Wise
By the time it's wine it IS dead. (and pickled)(;>)
--
Jack Wise
William L. Hartzell
Bad news: it sounds like you got a blue box RealTek NIC. Those don't
work. IF you got a black box Realtek NIC, then those would work. We
never found out what was done to change working chip into defective
chip. I've checked with Google -> groups and reviewed the history of
that chip
<http://groups.google.com/group/comp.os.os2.networking.tcp-ip/browse_thread/thread/340c3cf2ef3283d5/f4976fb1aebba0ff?hl=en&lnk=st&q=#f4976fb1aebba0ff>
if you want to read it.
I'd suggest using Google groups and advance search on these many
comp.os.os2.* newsgroups for answers that were given in the past. There
have been several well written expositions on how to setup the
networking, including a few by myself. BTW, the com.sys error is
because you assigned the serial port to another device, like you surmised.
Snydley
"William L. Hartzell" <wlhar...@tx.rr.com> wrote in message
news:485b06a8$0$5719$4c36...@roadrunner.com...
I read through it, but how do you know if you have a blue box or black box?
As far as defective goes, it's not defective since it works fine with
Windows, maybe there's just not a good driver available for it? Geez, I
really didn't want to put much money into this, but I suppose if I can find
a different NIC for cheap that WILL work with it I'll buy it.
I figured the problem was that I just didn't have the network setup
correctly. The lantran.log file says " IBM LANVDD is loaded and operational"
so I figured the NIC was operational, it was just something in my network
configuation that I don't have set up correctly.
At this point it's kind of pointless for me to try to configure my network
if I don't know if I have a NIC that will work with Warp4 or not. I've got
to figure that out 1st, and if this won't work with Warp, I'll have to get
one that will, or forgo the network altogether and just use the machine to
run my old software on and use Windows when I want to Network.
Thanks for your time and info.,
Snyde
Dave Yeo
Go here, http://www.7cities.net/~mckinnis/os2/ and download the NICPAK
package, read the documentation and try it. Hopefully your card will
work. If not go to a used computer store or goodwill etc and spend a
couple of bucks on a card. Just a couple of years ago most cards worked
with OS/2.
To configure, go to system setup and choose Adapters and Protocol
Services. Or type in mpts at a command prompt. Setup tcpip first and see
if you can ping other computers on your network.
For networking with win9x boxes you need to setup netbios over tcpip,
not the default netbios.
Really you also need to upgrade mpts etc but unluckily the site I used
for pointers to the file locations is now gone and I can't remember the
files or location to upgrade. Maybe someone else will chime in
Dave
Paul Ratcliffe
> Go here, http://www.7cities.net/~mckinnis/os2/ and download the NICPAK
> package, read the documentation and try it. Hopefully your card will
> work. If not go to a used computer store or goodwill etc and spend a
> couple of bucks on a card. Just a couple of years ago most cards worked
> with OS/2.
Get a 3Com 3C905. These never give any problems. The last ones I bought
cost £2 each off eBay.
> For networking with win9x boxes you need to setup netbios over tcpip,
> not the default netbios.
You don't "need" to do that. You could always install Netbios on Windoze.
Netbios is a better protocol for newbies to use because it doesn't require
any configuration, unlike TCP/IP.
Dave Yeo
> On Fri, 20 Jun 2008 04:13:31 GMT, Dave Yeo<dave....@gmail.com> wrote:
>
>> For networking with win9x boxes you need to setup netbios over tcpip,
>> not the default netbios.
>
> You don't "need" to do that. You could always install Netbios on Windoze.
> Netbios is a better protocol for newbies to use because it doesn't require
> any configuration, unlike TCP/IP.
Will plain Netbios work through a router?
Dave
Allan
> Will plain Netbios work through a router?
No, that is why it is much safer to use in home env.
As it is easier to setup, and faster too, it is a much
better solution for end users.
--
Allan.
It is better to close your mouth, and look like a fool,
than to open it, and remove all doubt.
Paul Ratcliffe
>>> For networking with win9x boxes you need to setup netbios over tcpip,
>>> not the default netbios.
>>
>> You don't "need" to do that. You could always install Netbios on Windoze.
>> Netbios is a better protocol for newbies to use because it doesn't require
>> any configuration, unlike TCP/IP.
>
> Will plain Netbios work through a router?
No of course it won't because Netbios is not a routable protocol. I suspect
however you don't actually want to route it anywhere in the majority of cases.
The term router is much misused, especially in home networks. You probably
mean "switch" or "hub" where you mis-used "router".
One of the benefits of Netbios is that you can't route it and inadvertently
expose yourself to security risks.
Alex Taylor
> A little while ago i reported a problem with a Warp 4 installation on a
> large hard disk (8 Gb). Turns out that even after modifying the
> installation floppies to allow for large disks, one has to make sure
> that the installation partition does not exceed 2 Gb. If it does, the
> installation program fails to install the networking code. After i
> reduced the installable partition to 2 Gb, everything installed perfectly.
I think adding
SET CONNECT_DASD=OFF
to CONFIG.SYS on Disk 1 is supposed to get around that problem...
--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00
Please take off hat when replying.
Fred Blau
<ab...@orac12.clara34.co56.uk78> wrote:
> On Sat, 21 Jun 2008 04:28:59 GMT, Dave Yeo <dave....@gmail.com> wrote:
> > ... Will plain Netbios work through a router?
> No of course it won't because Netbios is not a routable protocol. I suspect
> however you don't actually want to route it anywhere in the majority of cases.
> The term router is much misused, especially in home networks. You probably
> mean "switch" or "hub" where you mis-used "router".
> One of the benefits of Netbios is that you can't route it and inadvertently
> expose yourself to security risks.
The terminology here is confusing, at least to me. For example, I have
a Linksys WRT54G, which Linksys calls a "router". In the past I used
Netbios (I now use Netbios over TCP/IP) to share files between two
computers on my LAN. Is Linksys misusing the term "router"? Would you
call this device a "switch" or "hub"?
--
Fred Blau
(Change "NOSPAM@" to "systematics@" in my e-mail address)
Alex Taylor
wrote:
> something similar. So I edited Config.sys manually from a command prompt
> using "e" and removed the reference to that driver. Is there a way to do
> that with a program in OS/2, something like Device Manager in Windows? I
> then fdisked the drive and reinstalled, because I don't know how to add or
> remove a NIC card and drivers from OS/2. How do you do that?
Different types of driver have their own install utilities. The one for
networking drivers is "Network Adapters and Protocol Services" (MPTS.EXE).
Should be an icon under System Setup.
> This time when I reinstalled, and it prompted me to choose a NIC card I
> selected "Other" and installed the original Realtek driver I told you
> about. I checked the lantran.log file with "e" and this is what it says:
> ...
> Loading Realtek Fast Ethernet Network Adapter driver (3.23vk) [2005-12-05]
> Vendor=1186,1186 Dev.=1300,1301 Bus/Dev/Func-No= 0/10/0
> EtherID=@00055DD05F50
> The chip is RTL8139C.
> Network Line Speed is 100 Mbps / Full-Duplex Mode.
> Link configuration: Auto Negotiation enabled.
> Flow Control: Transmit:Disabled, Receive:Disabled.
> Parameters: IOBase = 0x7C00
> Interrupt Level = 3
> IBM LANVDD is loaded and operational.
> IBM OS/2 LAN Netbind
>
> To me it looks like it's working ok, but I've never gotten that "deep"
> into Networks,(Windows always handled that), so I'm not sure. The only
> questionable thing I see is the flow control. Should that be enabled, or
> is this the way it should be?
Depends on the driver. You're right, the messages do indeed imply that the
driver is correct and the card is working.
You may just need to configure TCP/IP correctly. There were some kinks in
Warp 4 as it was originally released, hopefully you can get them sorted.
See below...
> I've got everything working, that I can tell, except the Network and
> Internet. I did have 2 errors in Config.sys a "com.sys" and a
> "vcom.sys"not loading . I was wondering if maybe that was caused by me
> selecting Fax service during the install, but not having a fax-modem, so I
> manually rem'd those 2 lines out in config.sys and those errors went away.
Those are the serial port drivers. Does the machine have serial ports? If
not, then this message would be expected.
If it does, then this may be caused by the sound driver. ISTR that the
AWE driver could cause the COM drivers to barf on bootup if you didn't
manually add a magic parameter (/G, I think) to the driver in CONFIG.SYS.
(I know that was true for the AWE64 - I had one - but I'm not sure about the
AWE32, which I think you said you have...)
> I think my whole problem now with the network is I just don't know how to
> set it up. The only experience I've had with networks is with Windows and
> it takes care of all of this for you, pretty much.
Yeah, OS/2 can take a bit of fiddling, especially on older (pre-4.5)
versions.
Basically, for working Internet, you need to make sure that:
1. The NIC driver is installed. You seem to have this.
2. The networking protocol (i.e. TCP/IP) is installed and "bound" to the
NIC. You probably did this during install, but post the contents of
\IBMCOM\PROTOCOL.INI and we'll take a look.
3. Configure TCP/IP. DHCP in Warp 4 out of the box was a bit flaky, so I
suggest trying to get it working with static IP first. We can always
change that later once you know it works.
For static IP, you need to configure:
- IP address (if you have the default Netgear configuration, probably
192.168.0.something would be correct - I suggest you see what the
computer uses when booted to Win98, and enter that one).
- Subnet mask (almost certainly 255.255.255.0; again, copy from Windows).
- Default route (what Windows calls "gateway") - whatever the LAN-side IP
address of the Netgear router is.
- DNS server, whatever your Windows system uses (probably also the Netgear
IP address).
Let us know if you need any help getting that configured. You can use the
TCP/IP Configuration program, even though it's a bit ugly.
Alex Taylor
wrote:
> At this point it's kind of pointless for me to try to configure my network
> if I don't know if I have a NIC that will work with Warp4 or not. I've got
> to figure that out 1st, and if this won't work with Warp, I'll have to get
> one that will, or forgo the network altogether and just use the machine to
> run my old software on and use Windows when I want to Network.
I disagree. The only way to find out if it works is to configure the
network and see if you get somewhere.
Personally, given that the driver loads successfully, I suspect that your
NIC is working OK. You just need to configure it.
Paul Ratcliffe
> Personally, given that the driver loads successfully, I suspect that your
> NIC is working OK.
Probably, but it's not guaranteed. I have had NICs die on me. They would
transmit OK (as confirmed by IPTRACE receiving incoming traffic on another
system) but would not receive anything (when being Pinged from elsewhere
and running a local IPTRACE).
One of them just stopped working spontaneously one morning when I was
nowhere near the machine. That had me going over all the config for a while,
wondering what had changed when nothing had, until I went back to basics.
Paul Ratcliffe
>> > ... Will plain Netbios work through a router?
>
>> No of course it won't because Netbios is not a routable protocol. I suspect
>> however you don't actually want to route it anywhere in the majority of cases.
>> The term router is much misused, especially in home networks. You probably
>> mean "switch" or "hub" where you mis-used "router".
>> One of the benefits of Netbios is that you can't route it and inadvertently
>> expose yourself to security risks.
>
> The terminology here is confusing, at least to me. For example, I have
> a Linksys WRT54G, which Linksys calls a "router". In the past I used
> Netbios (I now use Netbios over TCP/IP) to share files between two
> computers on my LAN. Is Linksys misusing the term "router"? Would you
> call this device a "switch" or "hub"?
This device (as are all its peers) is a hybrid router-switch. This is where
the problem in the naming occurs. Anything on the LAN side goes into the
switch. The router has two ports - one which goes to the switch and the other
which goes to the WAN side.
As a switch is a layer 2 device, it will pass Netbios traffic (and indeed any
sort of Ethernet traffic you care to dream up) between the ports. A router is
a layer 3 device and will not pass Netbios traffic from the LAN side to the
WAN side. A router will only pass IP traffic.
Snydley
"Alex Taylor" <mai...@reply.to.address> wrote in message
news:mdq090pMZSKk-pn2-1yFbfrwWyPyH@localhost...
> On Thu, 19 Jun 2008 06:40:30 UTC, "Snydley"
> <snydley2R...@stny.rr.com>
> wrote:
>
>> I don't know how to add or remove a NIC card and drivers from OS/2. How
>> do you do that?
>
> Different types of driver have their own install utilities. The one for
> networking drivers is "Network Adapters and Protocol Services" (MPTS.EXE).
> Should be an icon under System Setup.
After messing around long enough I came across that utility. I was able to
change drivers for this NIC card with different Realtek drivers, in the
chance that I had the wrong one loaded, but this original one I used seems
to work best. I got errors from config.sys when I tried any of the others.
That's the thing, I DON'T know how exactly. I found the TCP/IP configuration
program, entered 192.168.0.3 as my IP address and 255.255.255.0 as the
subnet mask, but I don't know what to enter for the other values in that
config program.
>
>
>> I've got everything working, that I can tell, except the Network and
>> Internet. I did have 2 errors in Config.sys a "com.sys" and a
>> "vcom.sys"not loading . I was wondering if maybe that was caused by me
>> selecting Fax service during the install, but not having a fax-modem, so
>> I
>> manually rem'd those 2 lines out in config.sys and those errors went
>> away.
>
> Those are the serial port drivers. Does the machine have serial ports?
> If
> not, then this message would be expected.
It does, but I have them turned off in the BIOS to save the IRQs. I remmed
out com.sys and vcom.sys in config.sys.
>> I think my whole problem now with the network is I just don't know how to
>> set it up. The only experience I've had with networks is with Windows and
>> it takes care of all of this for you, pretty much.
>
> Yeah, OS/2 can take a bit of fiddling, especially on older (pre-4.5)
> versions.
>
> Basically, for working Internet, you need to make sure that:
> 1. The NIC driver is installed. You seem to have this.
> 2. The networking protocol (i.e. TCP/IP) is installed and "bound" to the
> NIC. You probably did this during install, but post the contents of
> \IBMCOM\PROTOCOL.INI and we'll take a look.
> 3. Configure TCP/IP. DHCP in Warp 4 out of the box was a bit flaky, so I
> suggest trying to get it working with static IP first. We can always
> change that later once you know it works.
>
> For static IP, you need to configure:
> - IP address (if you have the default Netgear configuration, probably
> 192.168.0.something would be correct - I suggest you see what the
> computer uses when booted to Win98, and enter that one).
> - Subnet mask (almost certainly 255.255.255.0; again, copy from Windows).
> - Default route (what Windows calls "gateway") - whatever the LAN-side IP
> address of the Netgear router is.
How do I find this? This is the kind of thing I don't know.
> - DNS server, whatever your Windows system uses (probably also the Netgear
> IP address).
How do I find that too? I have DHCP set up on my Windows drive so I've never
had to "mess" with those settings..
>
> Let us know if you need any help getting that configured. You can use the
> TCP/IP Configuration program, even though it's a bit ugly.
I'll go back through it with the info. you gave me here and see how I make
out.
Please, I can use all the help I can get with the TCP/IP setup. I can run
the program and enter the info., the problem is I don't know what values to
enter, or how to find them.
>
> --
> Alex Taylor
> Fukushima, Japan
> http://www.socis.ca/~ataylo00
>
> Please take off hat when replying.
I'd appreciate any help you can furnish with the TCP/IP and LAN setup.
Thanks,
Snyde
Mike Luther
Boy are those final words important! Unless you have no other choice you
should NEVER use the protocol NETBIOS OVER TCP/IP in the OS/2 network setup for
a system. The reason is that pathway creates one of the easiest ways for a
remote system to download files all over your OS/2 box from afar for virus and
corruption intentions!
True, modern Windows smash thee code doesn't, ordinarily, run on OS/2 boxes.
But that doesn't mean a remote system somewhere around the world to which you
have somehow connected can't put file after file after file in every directory
and subdirectory you have on your system! Which .. although not seen yet in
our world, CAN be made to run if you happen to have the WIN32 drivers
installed. Or CAN be made to run if you have ODIN or whatever and the
targeting is done just right.
As well, using NETBIOS OVER TCP/IP there is nothing to stop an action where you
get a copy of the remote machine's CONFIG.SYS and/or AUTOEXEC.BAT and startup
.CMD files. From there, as we currently use OS/2, there is nothing to prevent
the perp from simply adding a line of code and any custom executable you might
want, which runs at boot time .. or any time a DOS-VDM is opened, or any time
perhaps an new DCHP renewal is required by you IP or whatever.
Yes! I HAVE been hit by this one from afar on an OS/2 system with HUNDREDS of
files that had to be cleaned up on this box and were file, after file, after
file trounced into the quarantine directory by Norman!
I do *NOT* use NETBIOS OVER TCP/IP with OS/2 any more for this reason.
Very good advice Paul, in my opinion.
--
--> Sleep well; OS2's still awake! ;)
Mike Luther
Dave Yeo
Ok, this explains better. The original poster mentioned having a netgear
router so I thought router.
Dave
Snydley
"Alex Taylor" <mai...@reply.to.address> wrote in message
news:mdq090pMZSKk-pn2-1yFbfrwWyPyH@localhost...
Here's my protocol.ini file:
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
netbeui_nif = netbeui.nif
tcpip_nif = tcpip.nif
RTL8139_nif = RTL8139.NIF
[NETBIOS]
DriverName = netbios$
ADAPTER0 = netbeui$,0
[netbeui_nif]
DriverName = netbeui$
Bindings = RTL8139_nif
ETHERAND_TYPE = "I"
USEADDRREV = "YES"
OS2TRACEMASK = 0x0
SESSIONS = 254
NCBS = 255
NAMES = 29
SELECTORS = 15
USEMAXDATAGRAM = "YES"
ADAPTRATE = 1000
WINDOWERRORS = 0
MAXDATARCV = 4168
TI = 30000
T1 = 1000
T2 = 200
MAXIN = 1
MAXOUT = 1
NETBIOSTIMEOUT = 500
NETBIOSRETRIES = 3
NAMECACHE = 1000
RNDOPTION = 1
PIGGYBACKACKS = 1
DATAGRAMPACKETS = 10
PACKETS = 335
LOOPPACKETS = 8
PIPELINE = 5
MAXTRANSMITS = 6
MINTRANSMITS = 2
DLCRETRIES = 10
FCPRIORITY = 5
NETFLAGS = 0x0
[tcpip_nif]
DriverName = TCPIP$
Bindings = RTL8139_nif
[RTL8139_nif]
DriverName = RTSND$
MEDIUM = "_AUTO"
NETADDRESS = "192.168.0.3"
TXFIFO = 10
NOIRQ = 0
APM = 1
CARDBUS = 0
FLOWCONTROL = "TXA_RXA"
I'm getting a message from config.sys now when I boot up, it says:
socket:Network is down
Any idea what this is telling me, and how to fix it?
I removed NetBios socket access using MPTS hoping that would get rid of the
socket error, but it didn't
> 3. Configure TCP/IP. DHCP in Warp 4 out of the box was a bit flaky, so I
> suggest trying to get it working with static IP first. We can always
> change that later once you know it works.
>
> For static IP, you need to configure:
> - IP address (if you have the default Netgear configuration, probably
> 192.168.0.something would be correct - I suggest you see what the
> computer uses when booted to Win98, and enter that one).
> - Subnet mask (almost certainly 255.255.255.0; again, copy from Windows).
> - Default route (what Windows calls "gateway") - whatever the LAN-side IP
> address of the Netgear router is.
> - DNS server, whatever your Windows system uses (probably also the Netgear
> IP address).
>
> Let us know if you need any help getting that configured. You can use the
> TCP/IP Configuration program, even though it's a bit ugly.
>
> --
> Alex Taylor
> Fukushima, Japan
> http://www.socis.ca/~ataylo00
>
> Please take off hat when replying.
Thanks,
Snyde
Snydley
I went back into the TCP/IP LAN setup and added 192.168.0.1 for the gateway
and DNS server. I rebooted and nothing worked. So I went back in and
selected DCHP, saved, and rebooted.
When it rebooted I went to WebExplorer, typed in http://www.yahoo.com/ into
the URL field and I noticed in the upper right hand corner of the
WebExplorer window that the little computer monitor animation was moving,
but an error message come up and said "There is no viewer registered for
this type of file.Would you like to copy this file to your local disk?
ok/cancel" So I wondered if data was moving across the LAN from my router to
my computer, but I just couldn't view it. So I cancelled went back to the
desktop, and just for curiousity's sake I clicked on Connections > Web
Sites > OS/2 Related Web Pages > Norloff's OS/2 Shareware BBS
AND IT WORKED!!!!
I connected to http://www.os2bbs.com .
But this is what's happening: If I click the links that are in the Desktop >
Connections > Web Pages most of the pages will show up in WebExplorer and I
can view and navigate the site, if the website is still working.
If I manually type in an address, ie http://www.yahoo.com or www.yahoo.com
I get an error message saying that "There is no viewer registered for that
type of file. Would you like to copy the file to your local disk? And it
won't load the address into the browser. I wonder too if maybe it's "timing
out" too soon, because it puts that error on the screen rather quickly.
Any ideas what I need to do to get this working?
Thanks,
Snyde
Trevor Hemsley
<snydley2R...@stny.rr.com> wrote:
> Any ideas what I need to do to get this working?
Well, Webexplorer is prehistoric so updating to something made in the 21st
century might help!
Firefox or Seamonkey for OS/2 are both available and stand a much better chance
of working.
--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com
Steven Levine
at 01:54 PM, Paul Ratcliffe <ab...@orac12.clara34.co56.uk78> said:
Hi,
>> Personally, given that the driver loads successfully, I suspect that your
>> NIC is working OK.
>Probably, but it's not guaranteed. I have had NICs die on me. They would
>transmit OK (as confirmed by IPTRACE receiving incoming traffic on
>another system) but would not receive anything (when being Pinged from
>elsewhere and running a local IPTRACE).
I've seen a similar failure on working NICs when there is an interrupt
conflict. Typically, this occurs on older systems with some ISA cards.
Apparently, the driver does not need a working IRQ for transmit, but
definitely needs it for receive.
Steven
--
--------------------------------------------------------------------------------------------
Steven Levine <ste...@earthlink.bogus.net> MR2/ICE 3.00 beta 11pre14 #10183
eCS/Warp/DIY/14.103a_W4 www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------
Alex Taylor
wrote:
> > For static IP, you need to configure:
> > - IP address
> > - Subnet mask
> > - Default route
>
> How do I find this? This is the kind of thing I don't know.
>
> > - DNS server, whatever your Windows system uses
>
> How do I find that too? I have DHCP set up on my Windows drive so I've
> never had to "mess" with those settings..
Run 'winipcfg' from Start->Run under Win98 and you should be able to find
out what it's using from the box(es) that pop up.
Although I see from your subsequent messages that you have it all pretty
much sorted, now.
Alex Taylor
wrote:
> Here's my protocol.ini file:
--snip--
> [tcpip_nif]
>
> DriverName = TCPIP$
> Bindings = RTL8139_nif
>
> [RTL8139_nif]
>
> DriverName = RTSND$
> MEDIUM = "_AUTO"
> NETADDRESS = "192.168.0.3"
^^^^^^^^^^^^^^^^^^^^^^^^^^
I suggest you remove this particular setting. It doesn't mean your IP
address. I'm pretty sure it's an optional setting for overriding the
firmware MAC address in the Ethernet card.
Everything else looks fine, BTW.
Alex Taylor
wrote:
> When it rebooted I went to WebExplorer, typed in http://www.yahoo.com/
> into the URL field and I noticed in the upper right hand corner of the
> WebExplorer window that the little computer monitor animation was moving,
> but an error message come up and said "There is no viewer registered for
> this type of file.Would you like to copy this file to your local disk?
> ok/cancel" So I wondered if data was moving across the LAN from my router
> to my computer, but I just couldn't view it.
More correctly, the web page is loading, but WebExplorer simply doesn't
recognize the file type. It's probably choking on the embedded Javascript.
What this message is saying is: "I don't recognize this as viewable HTML, so
I assume it's a downloadable file." It's not a problem with your net
connection, just with WebExplorer.
> I wonder too if maybe it's "timing out" too soon, because it puts that
> error on the screen rather quickly. Any ideas what I need to do to get
> this working? Thanks,
It comes up quickly because it's only bothering to read the first few bytes
of the page before deciding it can't handle it.
Try a more old-fashioned website like http://hobbes.nmsu.edu and see if you
have more luck with that.
Your only problem here is that WebExplorer is 12 years old, and simply can't
handle a large number of modern websites. Imagine trying to surf the web
today using Netscape 1.0... same principle.
Eventually you'll want to install a browser like Mozilla, or at least
Netscape 4.61. But those will require some updates to your system first.
In the meantime, you might be able to use Links, which is crude but
serviceable:
http://hobbes.nmsu.edu/pub/os2/apps/internet/www/browser/links-2.1pre14.zip
This is a text-mode browser that runs in a command line window or full
screen. (It has a simple graphical mode too, if you run 'links -g'.)
Press 'Esc' while running to open the menubar, or 'g' to enter a URL.
You will also need to install the EMX runtime libraries in order to run
Links, but you will certainly want them on your system for other apps
anyway:
http://hobbes.nmsu.edu/pub/os2/dev/emx/v0.9d/emxrt.zip
And to unzip these files, you'll need the latest UNZIP.EXE:
http://hobbes.nmsu.edu/pub/os2/util/archiver/unz552x2.exe
(Run the self-extracting archive and move unzip.exe to a directory on your
PATH.)
There are various other web browsers available for OS/2. However, they will
almost all require you to update your system with more recent service
updates (FixPaks, in the parlance).
If you've got your system installed and running to your satisfaction, I
suggest that it's time to install FixPak 15, which is the last Warp 4 FixPak
that was made available to the general public.
I suggest you peruse my website for some basic information about how FixPaks
work:
http://users.socis.ca/~ataylo00/os2/fixpaks/index.html
(This may or may not be viewable in WebExplorer; it is viewable in Links.)
Rich Walsh
I have a TCP/IP-only setup using a RTL8139 and a static IP (IMHO,
the OS/2 DHCP client is too slow & makes my boot take too long).
The settings in the following files work perfectly for me.
--------------------------
x:\MPTN\BIN\setup.cmd
--------------------------
route -fh
arp -f
ifconfig lo 127.0.0.1
ifconfig lan0 192.168.0.51 netmask 255.255.255.0 broadcast 192.168.0.254 mtu 1500
hostid 127.0.0.1
route add default 192.168.0.1
Notes: Most home routers assign themselves an address of either
192.168.0.1 or 192.168.1.1 then assign 192.168.x.2 and up to DHCP
clients. Consequently, you want assign yourself an address that
the DHCP server is unlikely to use - in this case, 51.
If you can't tell from your Win settings what the 3rd octet is
(i.e. 0 or 1), open up IE, then try surfing to 192.168.0.1.
If that times out, try 192.168.1.1. Eventually, you'll get the
log in for the router. Once you know the router's address, adjust
all of the addresses above & below accordingly.
BTW... you can run setup.cmd as many times as you need or want;
there's no need to reboot to try different addresses.
--------------------------
x:\MPTN\ETC\RESOLV2
--------------------------
nameserver 192.168.0.1
Notes: this file gives the system the address of your DNS server;
in this case, it's your router.
--------------------------
x:\IBMCOM\PROTOCOL.INI
--------------------------
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
tcpip_nif = tcpip.nif
RTL8139_nif = RTL8139.nif
[tcpip_nif]
DriverName = TCPIP$
Bindings = RTL8139_nif
[RTL8139_nif]
DriverName = RTSND$
MEDIUM = "_AUTO"
NOIRQ = 0
APM = 1
CARDBUS = "NO"
Notes: this is for TCP/IP only. Once you have 'net connectivity,
you can go back and add in the Netbios stuff - if you actually
want it. For talking to WinXP or Mac OS X, I use SAMBA instead,
but we can defer that discussion for another day :-)
--
== == almost usable email address: Rich AT E-vertise.Com == ==
___________________________________________________________________
|
| DragText v3.9 with NLS support
Rich Walsh | A Distinctly Different Desktop Enhancement
Ft Myers, FL | http://e-vertise.com/dragtext/
___________________________________________________________________
William L. Hartzell
Steven Levine wrote:
> In <slrng5q20...@news.pr.network>, on 06/21/2008 at 01:54 PM,
> Paul Ratcliffe <ab...@orac12.clara34.co56.uk78> said:
>
> Hi,
>
>>> Personally, given that the driver loads successfully, I suspect
>>> that your NIC is working OK.
>
>> Probably, but it's not guaranteed. I have had NICs die on me. They
>> would transmit OK (as confirmed by IPTRACE receiving incoming
>> traffic on another system) but would not receive anything (when
>> being Pinged from elsewhere and running a local IPTRACE).
>
> I've seen a similar failure on working NICs when there is an
> interrupt conflict. Typically, this occurs on older systems with
> some ISA cards. Apparently, the driver does not need a working IRQ
> for transmit, but definitely needs it for receive.
>
I got a NIC that is failing to(while) preform(ing) the duplicate node
test with a return code of 8. This failure then causes the DHCPcp to
fail when
transmitting the request to the router's DHCPd for an address. But when
I start some program from the desktop that needs to be on the Internet,
everything connects after a short pause to get the local addy assigned.
Lantran.log logs the error as "LT00055: An unexpected error was returned
when the program tried to transmit the duplicate node address test. The
VFET2A_nif MAC return code is 8."
Can you think of any configuration error that would cause this?
Will Honea
> I went back into the TCP/IP LAN setup and added 192.168.0.1 for the
> gateway and DNS server. I rebooted and nothing worked. So I went back in
> and selected DCHP, saved, and rebooted.
> When it rebooted I went to WebExplorer, typed in http://www.yahoo.com/
> into the URL field and I noticed in the upper right hand corner of the
> WebExplorer window that the little computer monitor animation was moving,
> but an error message come up and said "There is no viewer registered for
> this type of file.Would you like to copy this file to your local disk?
> ok/cancel" So I wondered if data was moving across the LAN from my router
> to my computer, but I just couldn't view it. So I cancelled went back to
> the desktop, and just for curiousity's sake I clicked on Connections >
> Web Sites > OS/2 Related Web Pages > Norloff's OS/2 Shareware BBS
> AND IT WORKED!!!!
> I connected to http://www.os2bbs.com .
> But this is what's happening: If I click the links that are in the Desktop
> > Connections > Web Pages most of the pages will show up in WebExplorer
> and I can view and navigate the site, if the website is still working.
> If I manually type in an address, ie http://www.yahoo.com or
> www.yahoo.com I get an error message saying that "There is no viewer
> registered for that type of file. Would you like to copy the file to your
> local disk? And it won't load the address into the browser. I wonder too
> if maybe it's "timing out" too soon, because it puts that error on the
> screen rather quickly. Any ideas what I need to do to get this working?
Trevor has the best (and ultimately the only) solution. What you are likely
seeing is the web page is trying to load an image or script that WebEx
can't handle. That was a problem 5 - 10 years ago with WE and it certainly
hasn't gone away.
--
Will Honea
** Posted from http://www.teranews.com **
Snydley
> Trevor has the best (and ultimately the only) solution. What you are likely
> seeing is the web page is trying to load an image or script that WebEx
> can't handle. That was a problem 5 - 10 years ago with WE and it certainly
> hasn't gone away.
>
> --
> Will Honea
>
> - Show quoted text -
I'm trying to get both, or either, Seamonkey or Firefox to run on my
Warp4 system. I've downloaded and followed the instructions to install
it, but when I type firefox <enter> to get it to run from an OS/2
full screen prompt the curser drops down a line, then the desktop
comes on screen for maybe 10 sec., then it goes back to the OS/2
screen with the prompt blinking at d:\firefox. The browsers won't run.
I also tried adding it as a program to the desktop, and when I click
on the Firefox icon, nothing happens. Does anyone know what I'm doing
wrong, and why it won't run? Is it broken, or am I doing something
wrong. This is my 1st outing with Os/2 and there's alot I don't know
here!! On another note, the "wonderful and all powerful RoadRunner"
has stopped it's newsgroups feed to my local area, so now I have to
read and reply from www.google.com. I'm looking for a free feed
somewhere, if that's not possible I'll have to keep posting like this.
Does anyone know of one?
Thanks,
Snyde
Peter Brown
Do you have the required libc**.dll files installed? - check
Firefox/Seamonkey readme files for details or check here
http://www.os2bbs.com/os2news/Warpzilla.html
Regards
Pete
Snydley
wrote:
> Hi Snydley
>
>
>
>
>
> Snydley wrote:
> >> Trevor has the best (and ultimately the only) solution. What you are likely
> >> seeing is the web page is trying to load an image or script that WebEx
> >> can't handle. That was a problem 5 - 10 years ago with WE and it certainly
> >> hasn't gone away.
>
> >> --
> >> Will Honea
>
> >> - Show quoted text -
>
> > I'm trying to get both, or either, Seamonkey or Firefox to run on my
> > Warp4 system. I've downloaded and followed the instructions to install
> > it, but when I type firefox<enter> to get it to run from an OS/2
> > full screen prompt the curser drops down a line, then the desktop
> > comes on screen for maybe 10 sec., then it goes back to the OS/2
> > screen with the prompt blinking at d:\firefox. The browsers won't run.
> > I also tried adding it as a program to the desktop, and when I click
> > on the Firefox icon, nothing happens. Does anyone know what I'm doing
> > wrong, and why it won't run? Is it broken, or am I doing something
> > wrong. This is my 1st outing with Os/2 and there's alot I don't know
> > here!! On another note, the "wonderful and all powerful RoadRunner"
> > has stopped it's newsgroups feed to my local area, so now I have to
> > somewhere, if that's not possible I'll have to keep posting like this.
> > Does anyone know of one?
> > Thanks,
> > Snyde
>
> Do you have the required libc**.dll files installed? - check
> Firefox/Seamonkey readme files for details or check herehttp://www.os2bbs.com/os2news/Warpzilla.html
>
> Regards
>
>
> - Show quoted text -
Sure do. I went by the directions in the read me file. I wonder if
there's more to installing it than just unzipping it to an empty
directory on the hard drive and typing firefox? There was no installer
for firefox or the library files. I made a directory d:\firefox and
xcopied all of the firefox files from my F: cdrom drive,(with the /s
(subdirectory switch)), to the d:\firefox directory from a DOS window.
I then copied the library files to d:\firefox and when it didn't work
I also copied the library files to d:\os2\dll. Then went to d:
\firefox, in a DOS window, and typed attrib *.* -r /s in case they
were still read only. I'm trying to run Firefox from an OS/2 window
and full screen. I also tried to add it to the desktop via>
OS/2 PROGRAMS > SYSTEM SETUP > INSTALL PROGRAMS > SEARCH & SELECT
PROGRAMS TO ADD.
There is now an Additional OS/2 programs folder with Firefox in it.
When I double click it nothing happens. When I select it, right click
on it, select "Properties" the "Session" tab is "greyed out". I can't
select anything here. It makes me think it didn't install correctly,
or there's something else I have to do to install it.
Any idea?
Thanks,
Snyde
jch
> There is now an Additional OS/2 programs folder with Firefox in it.
> When I double click it nothing happens. When I select it, right click
> on it, select "Properties" the "Session" tab is "greyed out". I can't
> select anything here. It makes me think it didn't install correctly,
> or there's something else I have to do to install it.
> Any idea?
_____
I only installed the SeaMonkey browser and email client on my system.
If i recall correctly, i needed to upgrade the OS/2 system with fixpack
15 for SeaMonkey to work, and add the required libc.
--
Regards / JCH
Dave Yeo
> PROGRAMS TO ADD.
> There is now an Additional OS/2 programs folder with Firefox in it.
> When I double click it nothing happens. When I select it, right click
> on it, select "Properties" the "Session" tab is "greyed out". I can't
> select anything here. It makes me think it didn't install correctly,
> or there's something else I have to do to install it.
> Any idea?
> Thanks,
> Snyde
Your problem is that you copied the files in a DOS window. DOS (on OS/2)
only supports 8.3 filenames and the Mozilla apps use long filenames.
There is also the matter of Extended Attributes which may also get lost
in copying.
Best to copy the zip file to your OS/2 partition and then unzip.
You should also set MOZILLA_HOME in your config.sys to point to a
directory separate from where you install Firefox/Seamonkey. This will
be where your profiles are kept and you can update the apps without
losing your profile
Dave
jch
Forgot to mention versions i installed:
libc-0.5.1.exe
seamonkey-1.1.9.en-US.os2.installer.exe
--
Regards / JCH
Snydley
> On 06/24/08 07:42 am, Snydley wrote:
>
>
>
>
>
> > On Jun 24, 9:23 am, Peter Brown<losepeteSPAM-ME-...@ntlworld.com>
> > wrote:
> >> Hi Snydley
>
> >> Snydley wrote:
> >>>> Trevor has the best (and ultimately the only) solution. What you are likely
> >>>> seeing is the web page is trying to load an image or script that WebEx
> >>>> can't handle. That was a problem 5 - 10 years ago with WE and it certainly
> >>>> hasn't gone away.
> >>>> --
> >>>> Will Honea
>
> - Show quoted text -
Geez, this is starting to get ridiculous. Apparently, my OS/2 system
isn't seeing long filenames either, or is it the 16 bit Winzip ver.
6.3 that is in the Programs > Utilities folder that I'm trying to use
to unzip it? It sees firefox-3.0.en-US.os2.zip as firefox_.zip. Do you
know what I have wrong now? Do I have to use a different unzip
program, or enable long filenames in Warp or something?
Thanks for your patience, and help,
Snyde
Paul Ratcliffe
> Geez, this is starting to get ridiculous. Apparently, my OS/2 system
> isn't seeing long filenames either, or is it the 16 bit Winzip ver.
> 6.3 that is in the Programs > Utilities folder that I'm trying to use
> to unzip it? It sees firefox-3.0.en-US.os2.zip as firefox_.zip. Do you
> know what I have wrong now? Do I have to use a different unzip
> program, or enable long filenames in Warp or something?
For goodness sake, ditch DOS and Windows crap and use native OS/2 utilities.
DOS and 16 bit Windows do NOT support long filenames.
Eye Pikm
<stuf deleted>
> Geez, this is starting to get ridiculous. Apparently, my OS/2 system
> isn't seeing long filenames either, or is it the 16 bit Winzip ver.
> 6.3 that is in the Programs > Utilities folder that I'm trying to use
> to unzip it? It sees firefox-3.0.en-US.os2.zip as firefox_.zip. Do you
> know what I have wrong now? Do I have to use a different unzip
> program, or enable long filenames in Warp or something?
> Thanks for your patience, and help,
> Snyde
Did you install OS/2 on a Fat formated drive or HPFS?
Snydley
I've got a 1.5G drive partitioned as C ,DOS 6.22 and Windows 3.11
490Mb, and D as an extended partition and logical drive in HPFS 527Mb.
I also have E as another logical drive 527Mb. I have no long
filenames on this systems. I don't get it. Maybe that's my whole
problem with Firefox. I wonder if I shouldn't just repartition things
all over again, and just install OS/2 on this drive alone.
Thanks,
Snyde
Snydley
wrote:
I understand that, but overlooked it. It's been so long since I used
DOS and Win 3.11 that I didn't even think about it.
I never ran OS/2 before, so I don't know what to use. When I want to
copy things from my CD to my D: drive I've been using XCOPY *.* D:
\FIREFOX /S ,as an example, to copy everything including
subdirectories from my CD to my hard drive. I don't know what to use
to do that in OS/2.
Thanks for the help,
Snyde
Dave Yeo
xcopy * d: \Firefox /s at an OS/2 command prompt will work fine. OS/2
was meant to replace DOS and most of the commands are close to the same.
Using * instead of *.* will include files without an extension like
readme. HPFS preserves case but ignores it so FIREFOX, Firefox and
firefox are equivaliant. Help xcopy at a command prompt will bring up
the help.
For an unzip utility the simplest is unzip.exe which IIRC a version is
installed in the main install, or else look at Hobbes. There are a few
unzip utilities available which I don't use but I'm sure others can make
recomendations.
Dave
Dave Yeo
HPFS supports long file names. Thing is if you look from DOS you will
only see filenames that are 8.3. OS/2 had no short log=ng file names
like Win9x did. Also the basic system uses 8.3 filenames so it can be
installed on FAT.
Try going to an OS/2 command prompt and do
echo > "this is a long file name" then do a dir (on a HPFS partition)
An OS/2 command prompt is very similar to a DOS command prompt and
supports much the same commands and syntax
Dave
Snydley
>
> - Show quoted text -
When I do that an do a "dir" in an OS/2 window on my D: (OS2) drive it
shows "this is a long filename", (without quotes), listed along with
the other files in the root directory of D: Somewhere I'm loosing the
long filenames. This is how I'm doing things:
My main computer has Win XP on it. I've downloaded Firefox and
Seamonkey from Warpzilla on it and burned them to CD using Nero 6
Ultra Edition. When it's done burning, and I "look" at the CD with
Windows Explorer and I see long filenames. Then I carry the disk
across the room and put it in the CD burner in my OS/2 computer, a
233MMX Pentium, 128M Ram, NEC 3550A DVD-RW burner. When I look at it
from an OS/2 window, I see no long filenames. The file
firefox-2.0.0.14.en-US.os2.zip shows up as firefox_.zip. To make sure
it wasn't Nero, I just erased the CD, and copied the files to the disk
using Windows explorer. One thing here though, I got a warning from
Windows saying "The file "seamonkey-1.1.9.en-US.os2.installer.exe" has
extra information attached to it that might be lost if you continue
copying.The contents of the file will not be affected. Do you want to
copy the file anyway? Y/S/C" I select Yes but as before, when I look
at my CD in Windows explorer I have long filenames, when I put it in
the OS/2 machine I don't. Firefox ver. 2 shows up as Firefox~1.zip,
Firefox ver 3 shows up as Firefox_.zip. I don't think I have long
filenames enabled in the OS/2 machine for some reason. I did the
Advanced install when I installed it, and I don't remember there being
a choice whether or not I wanted long filenames. One thing though,
even though I formatted it in HPFS when asked, DOS and Win3.11 were on
the hard drive on the C: partition when I installed Warp. Could Warp
"see" that Dos was on there already and automagically turn off long
filenames because of it? I'm confused. I think I'll repartition again
with just OS/2 on the disk and see what happens.
Thanks,
Snyde
Mentore Siesto
wrote:
Hobbes is your friend. Also, on the original OS/2 distribution,
there's PKUNZIP2.EXE somewhere on path. pkunzip2 -d something.zip
should (note I wrote "should") do the job, but take my advice: it's
best to use the latest Info-zip Unzip.exe.
Mentore
Alex Taylor
wrote:
> > For an unzip utility the simplest is unzip.exe which IIRC a version is
> > installed in the main install, or else look at Hobbes. There are a few
> > unzip utilities available which I don't use but I'm sure others can make
> > recomendations.
> > Dave
>
> Hobbes is your friend. Also, on the original OS/2 distribution,
> there's PKUNZIP2.EXE somewhere on path. pkunzip2 -d something.zip
> should (note I wrote "should") do the job, but take my advice: it's
> best to use the latest Info-zip Unzip.exe.
Don't even try to use the pkunzip2 included with Warp 4, it's years ancient
and doesn't even support extended attributes. It'll blow up if you try to
unzip almost any OS/2-created zip file.
Alex Taylor
No, no. Stop.
You're confusing too many different issues here.
First. You can't run Firefox on your system if you haven't installed the
latest Warp 4 FixPak yet. Did you do that? Did you see my reply to you
a couple of days ago on that subject? (Given your questions about
unzipping, I assume you didn't.)
If it's disappeared from your newsreader, here it is from Google:
http://groups.google.com/group/comp.os.os2.misc/msg/eb041e273a50f545
Second. Download UNZIP from Hobbes. I included instructions in the
aforementioned message. That will let you unzip Firefox.
Third. You are using HPFS, therefore you have long filename support. No
worries there. The reason you can't see long filenames on the CD has
nothing to do with that. Rather, it's because Warp 4, as installed out of
the box, doesn't support the latest CD-ROM filesystem extensions (Joliet-3)
that Windows uses to create long filenames on CD. You won't see the long
filenames until you install the latest FixPak -and- the latest device
drivers. However, since Firefox is zipped up, you don't need to.
Everything should be just fine inside the zipfile (and it doesn't matter at
all what the zipfile itself is called.) Just unzip it to your hard disk
and you should be set... PROVIDED you've done all the above.
To summarize:
1. Install UNZIP. (Depending on the version, this may also require you to
install the EMX runtime as well, also described in my earlier post.)
2. Install FixPak 15 (and Device Driver Fixpak 2).
3. Install the latest LIBC 5 runtime required by Firefox.
4. Unzip Firefox to the hard disk and try running it.
Mentore
> On Wed, 25 Jun 2008 03:36:07 UTC, "Mentore Siesto" <mentore.sie...@libero.it>
> wrote:
>
> > > For an unzip utility the simplest is unzip.exe which IIRC a version is
> > > installed in the main install, or else look at Hobbes. There are a few
> > > unzip utilities available which I don't use but I'm sure others can make
> > > recomendations.
> > > Dave
>
> > Hobbes is your friend. Also, on the original OS/2 distribution,
> > there's PKUNZIP2.EXE somewhere on path. pkunzip2 -d something.zip
> > should (note I wrote "should") do the job, but take my advice: it's
> > best to use the latest Info-zip Unzip.exe.
>
> Don't even try to use the pkunzip2 included with Warp 4, it's years ancient
> and doesn't even support extended attributes. It'll blow up if you try to
> unzip almost any OS/2-created zip file.
*gasp* Sorry Alex, you're right and I was utterly wrong. Actually I
don't use pkunzip2 since years, and ISTR I experienced some problems
with it.
Sorry anyone! :-(
Mentore
Snydley
On Jun 25, 9:45 am, "Alex Taylor" <mail...@reply.to.address> wrote:
> Fukushima, Japanhttp://www.socis.ca/~ataylo00
>
> Please take off hat when replying.- Hide quoted text -
>
> - Show quoted text -
First off, THANKS SO MUCH for all the help you've given me, the system
is getting there, one step at a time it seems.
I unstalled Info-Zip's unzip and zip into a directory I created called
ZIP and added C:\ZIP to the PATH and LIBPATH line in config.sys using
"e" from an OS/2 prompt, then rebooted.
I've already installed fixpack 15, I didn't know about device driver
fixpack 2.
I downloaded device driver fixpack 2, burned it to CD and ran it from
the CD drive on my OS/2 machine. The Corrective Service Facility said
"There are no products on the target system to fix". So I xcopied
everything to C:\FIX and ran install.cmd again from the hard drive.
Same results. I previously ran the fixpack 15 is it included with that
maybe?
I installed the per the instructions on the Warpzilla site, "This
release requires the C runtime DLLs (libc-0.6.3) from
ftp://ftp.netlabs.org/pub/gcc/libc-0.6.3-csd3.zip"
I unzipped them to C:\Firefox,(I got rid of DOS, and put OS/2 on this
HDD by itself).
I'm going to re-install Firefox and the DLLs and then I'll let you
know how it goes.
Again thanks for all the help.
Oh, you were saying, "I'm confusing too many things". You are SO
right. This is my first time with OS/2 and I started my computer life
on DOS 3 and later Windows 3.1 so I'm not computer illiterate, but OS/
2 is making me feel like I am. :-)
Take care,
Snyde
Snydley
On Jun 25, 9:45 am, "Alex Taylor" <mail...@reply.to.address> wrote:
> Fukushima, Japanhttp://www.socis.ca/~ataylo00
>
> Please take off hat when replying.- Hide quoted text -
>
> - Show quoted text -
I went back through and did everything you said, come to find out I
had done everything already except get Unzip from Hobbes. I've got
that now. It turns out my problem was not having libc-0.5.1.exe
installed. In the readme file on the Warpzilla site it mentions
installing libc-0.6.3-csd3.zip, which I had already done, but no
mention of libc-0.5.1.exe. It wasn't until I unzipped everything this
afternoon, installed lib-0.6.3, and tried to run Firefox that Firefox
informed me that it couldn't find lib-0.5.1 and refused to load.
Whether or not the author of the readme assumed the reader would know
that the 0.5. library needed to be installed on the system, or they
forgot to mention it in the readme I don't know, but it's working now!
Thanks so much. It's very slow though, slow to come on screen. I think
that's do to the hardware on this machine, a P55C Pentium 233Mhz MMX
with 128M ram. I can live with it though. Any serious surfing I need
to do will be on my 1.93Ghz Dual - Core 2Gb Ram machine.
Now I only have 2 things left thst aren't working, long filenames from
the CD drive,(not a biggie), and my Network connection. I can get out
on the Net, but I can't connect to any of the other computers
connected to the router. Any hints or advice you can give me here?
Even if it was connecting, I don't know what program to use to view
the files on the other computers.
Thanks again for your help,
Snyde
Alex Taylor
> > > there's PKUNZIP2.EXE somewhere on path. pkunzip2 -d something.zip
> >
> > Don't even try to use the pkunzip2 included with Warp 4, it's years
> > ancient and doesn't even support extended attributes. It'll blow up if
> > you try to unzip almost any OS/2-created zip file.
>
> *gasp* Sorry Alex, you're right and I was utterly wrong. Actually I
> don't use pkunzip2 since years, and ISTR I experienced some problems
> with it.
The above said, it is possible to get a modern PKUNZIP2 and PKZIP2 for
OS/2, if you have WSeB, *CP or eCS by doing the following:
1. Download pkos2250.exe (from Hobbes or PKWare or somewhere else) and
unzip.
2. Dig out your WSeB, MCP/ACP or eCS 1.1/1.2/2.0 CD and find the
directory \OS2IMAGE\FI\FONTS.
3. Copy PKZIP.EXE off this directory on the CD, replacing the one that
came with the archive in step 1.
4. Install PKZIP.EXE, PKUNZIP2.CMD and PKZIP2.CMD to your path. You now
have a fully licensed copy of PKZIP 2.50 installed!
--
Alex Taylor
Fukushima, Japan
Alex Taylor
> > To summarize:
> > 1. Install UNZIP. (Depending on the version, this may also require you
> > to install the EMX runtime as well, also described in my earlier
> > post.)
> > 2. Install FixPak 15 (and Device Driver Fixpak 2).
> > 3. Install the latest LIBC 5 runtime required by Firefox.
> > 4. Unzip Firefox to the hard disk and try running it.
>
> First off, THANKS SO MUCH for all the help you've given me, the system
> is getting there, one step at a time it seems.
> I unstalled Info-Zip's unzip and zip into a directory I created called
> ZIP and added C:\ZIP to the PATH and LIBPATH line in config.sys using
> "e" from an OS/2 prompt, then rebooted.
You don't need to put the ZIP directory in the LIBPATH, but it won't really
hurt. (OTOH, it's a good idea to avoid overloading the LIBPATH - and the
PATH too, for that matter - because there are various problems associated
with letting them get overly long.)
I don't recommend using 'e' to edit CONFIG.SYS in general, because it tends
to append an EOF character to the end of the file. Normally this isn't a
problem, but it's possible to get into a situation where it might be.
I recommend you look for 'AE' on Hobbes, which is a more or less seamless
replacement for 'e' which is fair bit nicer to use.
(OS/2 also comes with an editor called EPM (Enhanced Editor), which is
decent if you reconfigure it heavily, but it has a pretty unpleasant default
configuration which makes it awkward to use. Also, reconfiguring EPM to any
significant extent is something of a black art, so I don't really recommend
trying to use it until you're more at leisure to play around with stuff like
that.)
> I've already installed fixpack 15, I didn't know about device driver
> fixpack 2.
> I downloaded device driver fixpack 2, burned it to CD and ran it from
> the CD drive on my OS/2 machine. The Corrective Service Facility said
> "There are no products on the target system to fix". So I xcopied
> everything to C:\FIX and ran install.cmd again from the hard drive.
> Same results. I previously ran the fixpack 15 is it included with that
> maybe?
No, it isn't. This is a strange message... the only thing I can think of
offhand is that the prerequisite SYSLEVEL isn't getting created before the
install runs. I thought the FixTool was supposed to run it automatically,
but maybe it depends on which front-end you use - anyway, try running the
batch file FIXTPREP.CMD (I think it's called) before starting the FixPak
installation.
> Oh, you were saying, "I'm confusing too many things". You are SO
> right. This is my first time with OS/2 and I started my computer life
> on DOS 3 and later Windows 3.1 so I'm not computer illiterate, but OS/
> 2 is making me feel like I am. :-)
No problem. It's actually kind of nice to see a newcomer willing to dive
into OS/2, with all its assorted learning curves. :)
--
Alex Taylor
Fukushima, Japan
Alex Taylor
> I went back through and did everything you said, come to find out I
> had done everything already except get Unzip from Hobbes. I've got
> that now. It turns out my problem was not having libc-0.5.1.exe
> installed. In the readme file on the Warpzilla site it mentions
> installing libc-0.6.3-csd3.zip, which I had already done, but no
> mention of libc-0.5.1.exe. It wasn't until I unzipped everything this
> afternoon, installed lib-0.6.3, and tried to run Firefox that Firefox
> informed me that it couldn't find lib-0.5.1 and refused to load.
> Whether or not the author of the readme assumed the reader would know
> that the 0.5. library needed to be installed on the system, or they
> forgot to mention it in the readme I don't know, but it's working now!
I could've sworn that the website and the readme both list that as a
requirement. But they've just been redoing the website recently, so maybe
it got lost somewhere along the way...
> Now I only have 2 things left thst aren't working, long filenames from
> the CD drive,(not a biggie), and my Network connection. I can get out
> on the Net, but I can't connect to any of the other computers
> connected to the router. Any hints or advice you can give me here?
> Even if it was connecting, I don't know what program to use to view
> the files on the other computers.
Ahaha. Yes, the local network sharing stuff can be a bit cryptic. Partly
this is a weakness in OS/2's design (IBM kind of tends to assume that if
you're using it, you're probably a LAN administrator in a large corporation
who already has most of the attendant knowledge), and partly because new
releases of Windows love to make proprietary modifications to how things
work.
First, you need to make sure the correct network protocols are installed on
all sides. By default, Windows (up to XP, anyway) uses NetBIOS over TCP/IP
a.k.a. TCPBEUI. So you should install that protocol under OS/2 as well.
Depending on the settings you chose for networking during OS/2 installation,
then TCPBEUI might be installed already. OTOH... it might not be. You can
use MPTS to take a look.
Next, I suggest you take a look at this website:
http://www.mit.edu/afs/athena/activity/o/os2/www/peer/WARPPEER.HTM
It does a far better job of explaining the incantations than I could here.
Some of the details a slightly out of date (for instance, the latest Peer
FixPak is now IP08414, not 8406), and I'd quibble a bit with some of his
background information, but all the practical stuff is basically correct.
Once you have the protocols configured, you need to make sure you use the
same userid/password on all computers you want to share resources between.
Under Warp 4, the logon program is buried somewhere under Connections, but
you may find it easier to just run 'logon /v:none' and enter whatever your
Windows username/password combination is. Then, if the network protocol
ducks are all lined up properly, you can do 'net view' from a command line,
or use the 'Shared Resources and Network Connections' GUI to try and see
the other systems.
However, there's another (yes, another) service update that I strongly
recommend you install before you dig into more advanced networking. The
update is MPTS v5.4 (to replace the v4.0 that comes with Warp 4), also
known as FixPak WR08610. This will fix a bunch of problems and also give
you a much more sophisticated TCP/IP stack (it might help Firefox speed up
slightly, actually).
FWIW, all of the FixPaks I would recommend for a freshly-installed Warp 4
system are:
- Base FixPak 15 (or 17, if you have access to it*)
- Device Driver FixPak 2 (or 3, if you access to it*)
- MPTS FixPak WR08610 followed by WR08621.
- TCP/IP FixPak UN00980
- LAN FixPak IP08414
* Access to FixPak 15 and DD FixPak 3 were only available through a
particular IBM service subscription up until about 2006.
--
Alex Taylor
Fukushima, Japan
Snydley
On Jun 27, 9:14 am, "Alex Taylor" <mail...@reply.to.address> wrote:
> On Wed, 25 Jun 2008 19:55:29 UTC, Snydley <snydl...@stny.rr.com> wrote:
> > I went back through and did everything you said, come to find out I
> > had done everything already except get Unzip from Hobbes. I've got
> > that now. It turns out my problem was not having libc-0.5.1.exe
> > installed. In the readme file on the Warpzilla site it mentions
> > installing libc-0.6.3-csd3.zip, which I had already done, but no
> > mention of libc-0.5.1.exe.
> I could've sworn that the website and the readme both list that as a
> requirement. But they've just been redoing the website recently, so maybe
> it got lost somewhere along the way...
I guess it must have, but like I said it's working now, and that's
great!!
>
> > Now I only have 2 things left thst aren't working, long filenames from
> > the CD drive,(not a biggie), and my Network connection.
>
> Ahaha. Yes, the local network sharing stuff can be a bit cryptic. Partly
> this is a weakness in OS/2's design (IBM kind of tends to assume that if
> you're using it, you're probably a LAN administrator in a large corporation
> who already has most of the attendant knowledge), and partly because new
> releases of Windows love to make proprietary modifications to how things
> work.
Unfortunately, that's not me. :-) I'm just a retired slob that's
somewhat of an enthusiast. :-)
I ran a Fidonet BBS in the late '80's, early '90's, and alot of my
fellow sysops were running their BBS software on OS/2. Mine was
Windows 95 specific,(Winserver), so I missed out on all of that
fun. :-)
This is GREAT info!!! Thanks so much! I'm gonna check it out now!!
> --
> Alex Taylor
> Fukushima, Japanhttp://www.socis.ca/~ataylo00
> Please take off hat when replying.
Snyde
Dave Yeo
> lots of interesting stuff about installing and updating OS/2
[...]
As a short cut I'd suggest you check out OS2MT at this site,
http://www.os2mt.tk.
Though I notice it hasn't been updated since April, most of the updates
should still work
Dave
Paul Ratcliffe
>>> Will plain Netbios work through a router?
>>
>> No of course it won't because Netbios is not a routable protocol. I suspect
>> however you don't actually want to route it anywhere in the majority of cases.
>> The term router is much misused, especially in home networks. You probably
>> mean "switch" or "hub" where you mis-used "router".
>> One of the benefits of Netbios is that you can't route it and inadvertently
>> expose yourself to security risks.
>
> Boy are those final words important! Unless you have no other choice you
> should NEVER use the protocol NETBIOS OVER TCP/IP in the OS/2 network setup for
> a system.
I disagree. It is safe if you take the correct precautions.
> The reason is that pathway creates one of the easiest ways for a
> remote system to download files all over your OS/2 box from afar for virus and
> corruption intentions!
Yes, but anyone with half a brain doesn't connect directly but rather via
a NAT router and/or firewall etc.
> Yes! I HAVE been hit by this one from afar on an OS/2 system with HUNDREDS of
> files that had to be cleaned up on this box and were file, after file, after
> file trounced into the quarantine directory by Norman!
You are a fool then if you haven't got your network configuration right and
you connect your machine directly to the internet.
> I do *NOT* use NETBIOS OVER TCP/IP with OS/2 any more for this reason.
>
> Very good advice Paul, in my opinion.
It wasn't advice. I don't advise anyone not to use Netbios over TCP/IP if
they want to and they have appropriate security.
Philip Nienhuis
Just to add a little (and getting a bit OT):
While plain NetBIOS (aka NETBEUI) has the "security benefit" of not
being routable, that benefit only holds on cabled LANs.
There may be some issues as soon as your NetBIOS LAN gets to be wireless:
1. One wifi, the benefit in question gets a bit attenuated as anyone may
eavesdrop on your connection using appropriate tools. A thing to
remember when you connect your file sharing enabled laptop to some
public hotspot. In addition, such hotspots rarely have encryption
enabled, so you lose that security layer to start with.
While a properly setup firewall may shield intrusion that tries to
(mis)use NetBIOS over TCP/IP (either cabled or wifi), it won't help to
protect against intrusion (mis)using NetBIOS "over wifi", as a firewall
can only affect IP-based protocols.
The only protection left is probably that few people nowadays use
NetBIOS/NETBEUI for file sharing anyway, so hackers hopefully can't be
bothered.
My conclusion is that at least on wifi, NetBIOS over TCP/IP is arguably
safer than plain NetBIOS.
2. Many newer wifi routers (actually the built-in access points) only
support IP based protocols (UDP, TCP, ICMP, ...) but no plain NetBIOS
anymore. Consequently, file & printer sharing across such wifi stuff
would work only with NetBIOS over TCP/IP.
E.g. my 4 yr-old Linksys WAP54G access point supports NetBios (NETBEUI)
& IPX/SPX, but a recently purchased Asus WL-330gE doesn't, not even in
plain AP mode.
Now, as current Genmac (or maybe it's the combination of genmac/wlan) is
not very reliable anymore with plain NetBios, all of the above may
become somewhat moot. But for older wifi equipment it still holds.
Philip