Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Martin_1962]

Was that BT?

I remember reading about it

IP vs IPX - with dos apps using a thunking layer for IP, IPX wins every time. With Win32 apps no problem either way.

TCP/IP stack on a DOS machine and it's pretty much 100% utilised.

IIRC, IPX was more efficient on half duplex links because it's not windowed so less collisions. Increase the RTT and it crawls along though. Crikey! this brings back some memories.

Kevin

I have played with a few dos client server clients and some were deadful.

Slowest was an AS/400 client (WIN/400), the AS/400 disk thrashed and the Clipper app dragged along.

Due to problems with the AS/400 they dropped in a Netware 4.10 server with ADS went like stink. We ran accounts link to AS/400 and most of our data on the Netware box, with 2 C/S links.

The move to AS/400 never took place and eventually the AS/400 accounts system was replaced with a PC system.

Fastest by far with Clipper was IPX client with hot Netware server and ADS 7.1.

[oceansoul]

the cabling and all that is how it was left by systems. Were in the process of tidying up the cabinet :p thats why we was intrested in what it does lol

[TheBoy]

actually the switch is a catalyst 3550 layer 3 switch, it is end of sale but still supportable for a year or so. The routers on the other hand are end of sale and end of support, so really should be replaced if they are mission critical.

cheers Tom

I wouldn't mind betting its configured and set up as a layer 2 switch....   ...which would be a waste when I'm after replacing a 2900XL with a layer 3 one (my 2900 is old one, no layer 3 capability)

[TheBoy]

Was that BT?

I remember reading about it

IP vs IPX - with dos apps using a thunking layer for IP, IPX wins every time. With Win32 apps no problem either way.

TCP/IP stack on a DOS machine and it's pretty much 100% utilised.

IIRC, IPX was more efficient on half duplex links because it's not windowed so less collisions. Increase the RTT and it crawls along though. Crikey! this brings back some memories.

Kevin

I have played with a few dos client server clients and some were deadful.

Slowest was an AS/400 client (WIN/400), the AS/400 disk thrashed and the Clipper app dragged along.

Due to problems with the AS/400 they dropped in a Netware 4.10 server with ADS went like stink. We ran accounts link to AS/400 and most of our data on the Netware box, with 2 C/S links.

The move to AS/400 never took place and eventually the AS/400 accounts system was replaced with a PC system.

Fastest by far with Clipper was IPX client with hot Netware server and ADS 7.1.

A lot of that is the quality of the stack.  The original monolithic netware driver was far quicker than the later odi ones (though an utter bitch to manage).

Used to look after some dos boxes that had 3 NICs, 1 for IPX to talk to a Novell Knitware server, 1 for IP for remote management, and one with OSI TP4 for X400 connectivity.  And the application needed about 400k memory - that was always a challenge with the 3 stacks!

[tomh]

actually the switch is a catalyst 3550 layer 3 switch, it is end of sale but still supportable for a year or so. The routers on the other hand are end of sale and end of support, so really should be replaced if they are mission critical.

cheers Tom

I wouldn't mind betting its configured and set up as a layer 2 switch....   ...which would be a waste when I'm after replacing a 2900XL with a layer 3 one (my 2900 is old one, no layer 3 capability)

most of them are TB, I have a couple in my rack at home, what do you need exactly? If you have the cash there is a 8port 3560 layer3 with poe now I was thinking of getting for the house I can get a price for you if you want.

tom

[Martin_1962]

Was that BT?

I remember reading about it

IP vs IPX - with dos apps using a thunking layer for IP, IPX wins every time. With Win32 apps no problem either way.

TCP/IP stack on a DOS machine and it's pretty much 100% utilised.

IIRC, IPX was more efficient on half duplex links because it's not windowed so less collisions. Increase the RTT and it crawls along though. Crikey! this brings back some memories.

Kevin

I have played with a few dos client server clients and some were deadful.

Slowest was an AS/400 client (WIN/400), the AS/400 disk thrashed and the Clipper app dragged along.

Due to problems with the AS/400 they dropped in a Netware 4.10 server with ADS went like stink. We ran accounts link to AS/400 and most of our data on the Netware box, with 2 C/S links.

The move to AS/400 never took place and eventually the AS/400 accounts system was replaced with a PC system.

Fastest by far with Clipper was IPX client with hot Netware server and ADS 7.1.

A lot of that is the quality of the stack.  The original monolithic netware driver was far quicker than the later odi ones (though an utter bitch to manage).

Used to look after some dos boxes that had 3 NICs, 1 for IPX to talk to a Novell Knitware server, 1 for IP for remote management, and one with OSI TP4 for X400 connectivity.  And the application needed about 400k memory - that was always a challenge with the 3 stacks!

Hmm extended memory linkers

[TheBoy]

Was that BT?

I remember reading about it

IP vs IPX - with dos apps using a thunking layer for IP, IPX wins every time. With Win32 apps no problem either way.

TCP/IP stack on a DOS machine and it's pretty much 100% utilised.

IIRC, IPX was more efficient on half duplex links because it's not windowed so less collisions. Increase the RTT and it crawls along though. Crikey! this brings back some memories.

Kevin

I have played with a few dos client server clients and some were deadful.

Slowest was an AS/400 client (WIN/400), the AS/400 disk thrashed and the Clipper app dragged along.

Due to problems with the AS/400 they dropped in a Netware 4.10 server with ADS went like stink. We ran accounts link to AS/400 and most of our data on the Netware box, with 2 C/S links.

The move to AS/400 never took place and eventually the AS/400 accounts system was replaced with a PC system.

Fastest by far with Clipper was IPX client with hot Netware server and ADS 7.1.

A lot of that is the quality of the stack.  The original monolithic netware driver was far quicker than the later odi ones (though an utter bitch to manage).

Used to look after some dos boxes that had 3 NICs, 1 for IPX to talk to a Novell Knitware server, 1 for IP for remote management, and one with OSI TP4 for X400 connectivity.  And the application needed about 400k memory - that was always a challenge with the 3 stacks!

Hmm extended memory linkers

Not poss - all 16 bit stacks, and 16 bit app...  ...you're stuck with the 700Mb you can make available....

[AndersH]

You're all reminding me that I have my CCNP switching exam on Wednesday and I really need to do some revision