Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - halgorithm

Pages: [1] 2
IBM to open source OS/2 - very unlikely.

Do a little bit more Googling, you'll find articles like this:

Hardware / Re: Looking for a printer
« on: 2009.04.06, 21:24:38 »
I've had very good luck with the HP Laserjet 4 PS drivers to pretty much any new HP printer (color or not).  My trick is to not print through a print server, but directly to the printer via LPRPORTD service using the IP address.  It works pretty snazy and it's pretty fast.

Applications / A decent / better 3270 mainframe client
« on: 2009.04.03, 23:05:58 »
Currently using the old ibm personal communicator 4.2 and it's not rendering some of our mainframe screens properly (some of the lines or dashes appear as SSSS symbols) and I'm looking at other solutions.  I went through hobbes and I didn't find one I really liked that was gui operated.

Anyone have any other opinions / thoughts?  Thanks!

Halgorithm,  you need to check the nif file the nic is using and see what it says about slots.

The following is from RTL8139.nif that I use on all but one of my computers.

  Display    = "Identify card using Bus Number:"
  Type       = Hexadecimal
; Default    = "0"
  Optional   = Yes
  Editable   = Yes
  Range      = 0-31
  Help       = "This parameter selects correct card of multiple network
                adapter cards. It is the PCI BUS number of the adapter card.
                The value of this parameter is 0x00-0x1f.
                Use together with Device Number."

The nif file you are using needs something like the above to work without asking for a slot number.

Most cards are set to optional but I have noticed that some intel cards require a number even if they are the only card.  This may be your problem but as I don't have a copy of the nif file you are using I can't say for certain.

Ah... interesting to note that the Intel NIF doesn't have a "default" option listed under the 'busno' / 'SLOT' area.  In addition, doesn't inform the user on how to configure the slots, etc.  I read through the help file with no avail, it didn't tell me squat.  I would have thought it had a SLOT field to populate or at least have it semi-ed out.  I specified a blank SLOT= field and it didn't change, nor did the messages go away when I had put SLOT = 0x0160 or SLOT = 0160 in the area.

I'll try using the Default field under SLOT, see if I can squelch that annoying message about it not being configured when it gets configured somehow automagically. 

Code: [Select]
   display = "Slot/Device Identifier"
   type = Hexadecimal
   range = 0-1FFF
   optional = YES
   editable = YES
   help = "Use of this parameter is only required in systems with more than one
 adapter installed. If you are installing more than one PCI adapter: 1) complete
 the configuration process, but leave the Slot field blank for each driver;
 2) restart the system and record the list of Slots that each driver displays;
 3) complete the configuration by assigning one of the values from the list to
 the Slot parameter of each driver. Leave the field blank if you have only one
 adapter installed."

Here's a PCI info regarding the NIC...

Code: [Select]
Vendor 8086h Intel Corporation
 Device 100Eh 82540EM Gigabit Ethernet Controller
 Command 0117h (I/O Access, Memory Access, BusMaster, MemWrite+Invalidate, System Errors)
 Status 0230h (Has Capabilities List, Supports 66MHz, Medium Timing)
 Revision 02h, Header Type 00h, Bus Latency 40h
 Self test 00h (Self test not supported)
 Cache line size 64 Bytes (16 DWords)
 PCI Class Network, type Ethernet
 Subsystem ID 01511028h PRO/1000 MT Network Connection (Guess Only!)
 Subsystem Vendor 1028h Dell Computer Corp
 Address 0 is a Memory Address (anywhere in 0-4Gb) : FEAE0000h
 Address 2 is an I/O Port : 0000DF40h
 System IRQ 9, INT# A
 New Capabilities List Present:
   Power Management Capability
     Supports power state D1
     Current Power State : D0 (Device operational, no power saving)
   PCI-X Capability
     Primary AD Bus size is 32-bit
     Primary AD Bus Maximum Speed in PCI-X mode is 66MHz
   Message Signalled Interrupt Capability
     MSI is disabled
     MSI function can generate 64-bit addresses

...most probably a left over artifact from the time he tried with a physical nic in a PCI slot in which all he needs to do is either use MPTS to remove the card  or edit the protocol.ini in ?:\ibmcom...

Maybe it's a PEBKAC, but I can't determine where I need to change it in MPTS - I only see a single network card (the on board one) in reference.  My protocol.ini doesn't reference to any other driver besides netbeui, tcpip, and the e1000 (not the 3com card I had in the machine initially)

I've also skimmed through the ibmlan.ini and again, not seeing the variable to change. 

What I'm going to try to do is 'remove' the lan adapter and all protocols, treat the machine like it has no nic.  Then, proceed to try to install it fresh after a powercycle.  Won't use NICPAK this next time around either.


No go gentlemen, even on a fresh system it does the same thing.  It is either protocol related with tcpip / netbios running or it is the simple fact that the .ini or .nif file requires modification from its original state.

I have the hex address of the card being at 0x0160 and I just can't figure out where to plug this in as an option.

You could try the IBM drivers at:

OKAY!  Used these drivers in MPTS and it is now working, powered down, unplugged, up, and working.

Thanks for all your help everyone!

*note:  still get that slot not specified for driver instance 1 message, but the DHCP is working now, it does get the address, it's printing and I can get logged into all my applications.

If both cards are Intel cards, you need to set the slot ID via MPTS. If such is the case, let me know and I will help you do so (if you havent figured out how yourself).


I only have one Intel card I'm working with (the onboard) but do you think that it would benefit me if I did configure the setting for what slot it is in?

Did you try this one?*&lang=eng&strOSs=10&submit=Go%21

Yes indeed.  Tried it before posting.  The driver version with these is 4.17, as are the ones off of Hobbes.  Also tried the 100mb ones, and those drivers refuse to actually work properly.  At least with the 4.17s, it installs, but fails to DHCP.

Did a pci probe to check and yes, I do have the right drivers.  Wrong version, maybe.  

A thought... maybe I have them misconfigured.  The reason I believe this is because of the initial error message in the subject and possibly a setting that wasn't configured on my part (not that I'm supposed to configure a setting in protocol.ini, but wouldn't be the first time I had to change a setting).

When I'm in MPTS and confirming the protocol stack that when I look at TCPIP config, it has nothing listed in there as an option set.  

Attached is my LANTRAN and it hasn't helped me.

Oh this is a great help, thanks for the info!  I didn't have any idea something like genmac existed.  This will more then likely fix my issues!

Thanks again!


Me again.  Looks like GenMac may not support the card.  Looked it up on Intel's site.

C91016-xxx IntelĀ® PRO/1000 MT Desktop PWLA8390MT RJ45, 10/100/1000, PCI, 82540EM
VendorID:8086, DevID:100E

Read through the GenMac docs, and it doesn't have this driver listed nor specified, or supported.

I'd like to see if I can:

A) find a driver, if it works the same, from my eCS livecd.  Not even sure if it is possible or not. 
B) obtain the older drivers (3.63) from someplace.  Hobbes doesn't have them.
C) find some 10mbit half duplex reference driver that works.  I could care less if it's at gigabit speed, or even megabit speed.

*First, I may not be entirely sure if this belongs in the network portion of the forum, but I believe that it has something to do with the hardware.

I have a Dell GX270 with an onboard NIC that I have been struggling to get working correctly on OS/2 Warp 4.52.  I've ran out of expansion cards that I have been using in the past for network connectivity.  I use the most recent OS2 drivers from hobbes for this chipset.

Now, the kicker (which is driving me bozonkers).  It works, but doesn't work.  Meaning it fails on the DHCP bootup (gives error) but then it magically obtains an IP address assignment somehow.  I can ping it from another machine, but I'm not able to authenicate with the network, and this same network port works just fine with another machine that has a different NIC.   This same machine works with a different NIC in an expansion slot (a 3com card) and it authenticates just fine.

I used MPTS to install the drivers, which I obtained from hobbes.  I did a pcisniff on it to gather the information regarding the chip onboard and no errors installing.  I've also installed fresh and used this NIC along with this set of drivers and a different set from  No change in issue.

Any ideas? I've muddled through the ini files and stil can't sauce this issue out.


I was wrong with it getting an IP address.  The DCHP tools say it will release but won't get a new valid lease.  I think it retained the IP address from when I had an expansion card plugged into the machine.  Do I need to try different drivers again or something?

Slightly munged ini files?  ???  Sorry, I'm not understanding you completely.

I've removed all startup items from the Startup folder in the WPS and my startup.cmd calls my other logon, which the first thing after the Requester services launches is it authenticates wtih the domain.  This window is expected; however, my original posting referrs to a window that opens when the Requester service launches, it's almost as if the requester service itself is trying to authenticate with the domain, but it incorrectly does so.  THAT was the dialog box I wanted to separate from the Domain authentication logon.  Here, next time I've got a momento (between this and Vista support) I'll take some screenshots of what I'm talking about in my virtual pc, that is if it comes up on that thing. 

I think it really has something to do with the protocol.ini file or some sort of config, but I can't determine this.  It may even have something to do with the way OS2 talk to a Windows 2k3 server or a default file share and it wants to authenticate.  I have no idea really.

In the startup.cmd file right after the reqeuster service, I call the login.bat script that does the

NET USE K: \\server\share
NET USE LPT1 \\server\printer

and then I get the proper login prompt as I want (aka just like the NET USE prompt, because if I do this it works)

Yeah, the very long / tall prompt I'd just like to squelch and not have to see it.  I found out yesterday when I went into the ibmlan.ini and changed the DOMAIN = ABC variable to something else, it compes up in the long and tall dialog prompt box with that domain...

So yes, it looks like it is something inside of the ibmlan.ini or somwhere else and the local os/2 machine is trying to authenticate as itself to the domain.  So you're right Rob with the fact that it's probably set to default with workgroup logon and I can change this and it will stop this annoying prompt?  I'm going to go and give it a try really quick-like and get back.

Everything works, but this is annoying me and my users...

When the machine starts up, it launches requester service (since it's needed to talk to Windows file share) and I'm finding before I need to put in credentials for a file share I'm mapping to manually (via NET USE), OS/2 wants to map this 'LS' for network and printer file resources.  It wants to do this with a username and password prompt that is different than others I have seen, which has never worked any username or password I know.  We have just been cancelling it and then using the other domain logon prompt, which has always worked and maps a network drive successfully.

My question - How do I prevent this LS prompt from coming up?  I've tried digging through the ibmlan.ini file and thought I configured it properly.  I must have missed something. Is it even in this area to configure the change to stop this LS prompt?  LS isn't even the workgroup name or domain name, so I'm at a loss.

I'm guessing that when OS/2 is talking to the DC and then it 'sees' a guest share for, let's say like a default share for all users, that it wants to map to this guest share and comes up with a prompt - which i don't want to log into and doesn't work with any known userid/password.  I would rather not see this and only have the logon to domain prompt when I manually launch the NET USE command to the DC.

Any ideas?  Attaching the IBMLAN file.  What I can't figure out is that it says there are 40 config options, but there are 42 characters in the wrkheuristics line.

It's working now and I didn't change anything in the config.sys - unplugged and plugged it back into a different USB port.  Gofig.

My objective is to get the USB feature (which is one plug, mouse and keyboard USB via KVM) working on a Warp 4.52 box via a KVM.  The keyboard and mouse themselves are PS/2. 

I know this works, because I have a T30 I have the same version of OS2 running on - and while it is plugged into the docking station using one USB port, I can toggle back and forth between that machine and another with no issues.  In addition, I can also use both keyboard and mouse.  It has worked flawlessly.

However, using the same install disks, I have installed on a Dell GX270 and have been able to get the USB working for both keyboard and mouse - but then it is not usable when I have the one USB plug in from the KVM.   ???  It's almost like OS/2 doesn't even see the Keyboard and Mouse through that one USB cable, and it should.  I can go and plug in a free standing USB mouses and USB keyboards and both will work with ease and right away within seconds.  Unplugging and plugging in the KVM USB cable does nothing and no respose from any devices, even after waiting an hour.

I've managed to grab the config.sys (attached) from the IBM Thinkpad T30 and try to configure the changes to the desktop, but I have had no success.  I keep getting it incorrect on the desktop, and just don't know what lines I need to add or change on the other computer's config.

Googling didn't help me with this question.  The only other thread relating to KVMs I found on the forum was saying something about how someone was splicing wires.  I know that I may lose my mousewheel function going through the Belkin, but that's a compromise I'd rather have.

Pages: [1] 2