Hello
   Hmmmmmm....comments or rather questions follow below...

 -------------- Original message ----------------------
From: Martin Rosenfeld 
> Mike,
> 
>   > When you installed RC2 - did you notice whether the selection for
> > PCI-COM ports was selected -
> I usually do check install COM ports. I think I forgot because COM.SYS 
> and VCOM.SYS were not in config.sys. After your message I added them and 
> rebooted.
> 
> > What config.sys entries do you have for *com.sys?
> 
> DEVICE=Q:\OS2\BOOT\COM.SYS
> DEVISE+Q:\OS2\MDOS\VCOM.SYS
> 
> > Do you need to specify the actual IRQs-I/O ports individually on the COM 
> > drivers in config.sys?
> 
> I never had to specify COM ports before. What syntax would I use to try?
> 
> Martin
> 
   This begins as entirely intellectual curiosity at this point since I
have for quite some time eschewed the use of the legacy parallel and serial
ports in order to free up their resources (early on even used scsi devices
to replace common serial and parallel devices) but I do seem to recall that
even waaay back on OS/2 v 2.0 (my very first true GUI and 32bit system) it
purportedly could handle 256 serial ports without conflict. It further
seems to me that this was at least partly possible through virtualization
so why the alleged need for assigned irq's in config.sys?  I tend to agree
with Martin that I don't think I ever had to assign them., but I'm not sure
how or why.  

  Dani pointed out some time ago that OS/2, at least at that point, was not
truly PlugNPlay (geez funny how that term seems archaic now) in that it did
not complement or override the bios and auto assign resources.  Since that
time however OS/2 and it's variants handles USB, SATA and other
hot-pluggable hardware.  Linux, beginning  with "hotplug" in
2.4.x kernels, and now with the advent of "udev" in kernels after
2.6.16, does very nicely at handling hot-swappable devices.  Windows, even
though it can stil get hung seemingly interminably trying to read even
non-existant CDs before reaching the desktop, at least for some time now
has handily handled USB devices and now does reasonably well with SATA
devices without having to reboot (and if any system LOVES to reboot as the
solution to virtually ANY problem it is windoze) and Apple has had real
hardware automounting "forever". Is there now a new layer for
OS/2 or eCS that has expanded on early virtualization or even something a
quant
um leap up that can handle hardware resources automatically? 

With Intel and others trying to wastecan the bios and turn over hardware
assignments to the OpSys or some layer of it, and with the pending total
abandonment of all legacy I/O, it might seem that in some timeframe
possibly within 5 years any OpSys unable to handle such issues may be
relegated to old motherboards and in some fairly short time afterward, the
scrapheap.  I have laughed at rumours of OS/2's demise too many times to
count but this area does seem ominous if we aren't headed in that direction
of automounting.  Anyone got the scoop on prposed progress in this
department?
Jimmy



[Non-text portions of this message have been removed]



 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 Your email settings:
    Individual Email | Traditional

 To change settings online go to:
    http://groups.yahoo.com/group/os2hardware/join
    (Yahoo! ID required)

 To change settings via email:
    mailto:os2hardware-digest{at}yahoogroups.com 
    mailto:os2hardware-fullfeatured{at}yahoogroups.com

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

---