Conference noted::windows95

2860.0. "CMD driver on Venturis and Win95 problem?" by SIOG::CORCORAN () Wed Mar 19 1997 09:11

    Since I did a Win95 upgrade,I notice on my Venturis FP4100 (m/b v2,bios
    2.01) that the new CMD driver being used causes an extra drive to
    appear-I have drive C and D on the primary IDE,drive E and F (a CD)on
    the secondary.
    
    If I don't load MSCDEX,I get drive E as a copy of drive F.If I change the
    config setting to point to CMDX2.sys instead of CMDX.sys (both drivers
    are in the c:\windows\command directory) , things are ok except drive G is
    the CD and no F when I go into Win95,presumably because of the original
    upgrade making it the CD drive.
    
    It doesn't matter if the CD is master or slave on the secondary IDE.
    
    ( BTW,The original CMDX.sys driver in directory c:\quickcmd appears ok also
    if this is put in config.sys)
    
    
    

    Search for article Q151911 in the Microsoft Knowledge Base;
    Q132158 might also be useful (or a generic search on the word
    "CMD").  There are several known upgrade problems with CMD
    controllers which can result in bizzare results.
    
    Incidentally, I don't think you *need* to load any CMD drivers
    in CONFIG.SYS - at least, when I upgraded a Celebris FP90 the
    resulting CONFIG.SYS was pretty empty.
    
    P.S. The Knowledge Base is http://www.microsoft.com/kb

    Thanks,I'll check it out.I think you are right about the need for the
    CMD driver,during my t/s I left them out and the drives appeared ok.
    
    I seem to recall a TIMA article also where someone else also questioned the
    need for the CMD driver