Mtn_Bkng_Dave
Member
Laptops
I have been listening to this debate for many years now.
As of yet I have not run across this problem.
I only run Dell systems and have so for about as long as they have been in business.
The trick I have found is to not buy a "laptop" but rather a "mobile desktop". It will cost you a few pounds in weight but offers all the full featured functionality we have come to expect.
My current system has Serial, Parallel, Firewire, 10/100 Enet, Wireless Enet, and Modem built in. Check out the high end Inspiron series for more information. The cheaper Latitude series suffers the same issues you have discussed.
As far as serial compatibility......I run all versions of my programming packages currently on WinXP. This includes the older direct serial port access programs such as the SLC version 3 interface.
The trick to making these work is to create a shortcut to the program.
Under properties you can click the compatibility mode tab. Set it to run in WIndows 95 compatability mode and the serial issue is gone. This allows the program to directly access the port. Normal NT based windows operation is to allow the OS to manage the port. This WILL NOT work for older dos based software or early 16 bit windows packages.
I am yet to find one that will not work with this method.
Hope this helps,
Dave
I have been listening to this debate for many years now.
As of yet I have not run across this problem.
I only run Dell systems and have so for about as long as they have been in business.
The trick I have found is to not buy a "laptop" but rather a "mobile desktop". It will cost you a few pounds in weight but offers all the full featured functionality we have come to expect.
My current system has Serial, Parallel, Firewire, 10/100 Enet, Wireless Enet, and Modem built in. Check out the high end Inspiron series for more information. The cheaper Latitude series suffers the same issues you have discussed.
As far as serial compatibility......I run all versions of my programming packages currently on WinXP. This includes the older direct serial port access programs such as the SLC version 3 interface.
The trick to making these work is to create a shortcut to the program.
Under properties you can click the compatibility mode tab. Set it to run in WIndows 95 compatability mode and the serial issue is gone. This allows the program to directly access the port. Normal NT based windows operation is to allow the OS to manage the port. This WILL NOT work for older dos based software or early 16 bit windows packages.
I am yet to find one that will not work with this method.
Hope this helps,
Dave