GU>      Within the last month I finally took the plunge and rejected the 
GU> herd mentality by switching to OS/2 Warp 3.0.  Unfortunately I am having 
GU> a compatibility problem with LapLink version NU-2.01, it refuses to 
GU> communicate with my serial ports!
That's right.  LapLink won't work under OS/2 (unless you have a native 
version).  Why?  Because OS/2 doesn't allow programs to controller the 
hardware ports...that's precisely how LapLink does it's business.  I've even 
had problems with LapLink in Win95 in a DOS box...it runs for a while then 
craps out.  WinNT would have the same limitation.
Why does OS/2 not let programs control hardware ports?  Crash Protection.  If 
a program has completely control over a hardware port and it hangs on a 
call...it's locked the machine because it'll continue hammering that IRQ and 
nothing else will get service.  OS/2 intervenes in this case and tries to 
eliminate this problem.
Now this may not be exact to the numbers, but it's the general idea.  If 
you're system can dual-boot to DOS or something to that effect, that would be 
one way to get around it.
    Brian Hertziger   Mr. Homies' Computex    Mr. Homies' Neighborhood BBS
           (414) 325-7986  (BBS #1/Fax)    (414) 325-7987 (BBS #2)
 [Team OS/2] Member   RAR Reg. Site   ProBoard Beta Site  Allfix/2 Beta Site
___TheEdit v2.10
"- = ð áeta Testing an attitude with this one . . . ð = -"
OS/2: Bill Gates' worst nightmare!
--- [Mr. Homies' Computex]
---------------