• SIO and DOS

    From Sean Dennis@1:11/200 to Patrick Vittori on Fri May 9 01:43:42 2003
    Patrick,

    Are you loading VX00.SYS also when you load SIO?

    Later,
    Sean

    ---
    * Origin: Midnight's Hour - midnightshour.org - 618.529.9296 (1:11/200)
  • From Patrick Vittori@1:114/635 to Sean Dennis on Tue May 13 21:34:14 2003
    Evenin' Sean,

    Are you loading VX00.SYS also when you load SIO?

    In the config.sys file? Yup, its in there. Also load VSIO.SYS and have the default com.sys and vcom.sys device commands rem'd out.

    I also have it as part of the properties set for the DOS window that Ezy runs in (size=0 c:\sio\vx00.sys)

    Works on the dial-up side. erm... least
    I haven't *seen* any probs with that command loaded. :)


    Patrick

    --- Ezycom V2.01b001 00F90258
    * Origin: The Shaman's Inn - Quartzsite, Az (1:114/635)
  • From Sean Dennis@1:11/200 to Patrick Vittori on Wed May 14 01:50:48 2003
    *** Quoting Patrick Vittori from a message to Sean Dennis ***

    In the config.sys file? Yup, its in there. Also load VSIO.SYS and

    Hrm... not too sure then. What fixpack are you running? I'm trying to think what would be causing you not to see that. I had a problem with Nexus doing the exact same thing: it would see the ring, but not do anything with it.

    Later,
    Sean

    ---
    * Origin: Midnight's Hour - midnightshour.org - 618.529.9296 (1:11/200)
  • From Patrick Vittori@1:114/635 to Sean Dennis on Sat May 17 00:20:04 2003
    Evenin' Sean,

    In the config.sys file? Yup, its in there. Also load VSIO.SYS and
    Hrm... not too sure then. What fixpack are you running? I'm trying to

    FP12. Anything higher than that causes this ol' P200 mobo to have fits (leave it to IBM to create a CPU chip that causes probs w/ it's *own* OS. :/ ).

    think what would be causing you not to see that. I had a problem with Nexus doing the exact same thing: it would see the ring, but not do anything with it.

    I've received a few hints on what to do and what I _didn't_ do that may have caused a prob with the connection. Still backlogged at the worksite, so getting
    "to it" to run more tests is still about 3 weeks off.. :<

    Patrick

    --- Ezycom V2.01b001 00F90258
    * Origin: The Shaman's Inn - Quartzsite, Az (1:114/635)
  • From Sean Dennis@1:11/200 to Patrick Vittori on Sun May 18 10:44:48 2003
    Hello, Patrick.

    Replying to a message of Patrick Vittori to Sean Dennis:

    FP12. Anything higher than that causes this ol' P200 mobo to have
    fits (leave it to IBM to create a CPU chip that causes probs w/ it's
    *own* OS. :/ ).

    That's interesting... I'm going to upgrade to FP15 and install a kernel update (FP15's kernel has a problem with DOS and OS/2 apps accessing the com port at the same time: usually the DOS program loses).

    I've received a few hints on what to do and what I _didn't_ do that
    may have caused a prob with the connection. Still backlogged at the worksite, so getting "to it" to run more tests is still about 3 weeks off.. :<

    Yep. I'm going to work on the BBS today myself. I've put it off for too long...

    Later,
    Sean

    //hausmaus@midnightshour.org | http://midnightshour.org | ICQ: 19965647

    --- FleetStreet 1.27.3.8d
    * Origin: Happiness is being warped in a sea of windows. (1:11/200)