[Prev][Next][Index][Thread]

Re: Re[2]: E/D Win95 Drive Problem Update



I apologize.  I have never posted to list's before.  I posted A reply to 
Sean Kanes CDROM problem, but only sent it to his address.  I am no 
reposting the whole discussion for the benifit of any who might have been 
interested.

SEAN KANE WRITES THE ORRIGIONAL PROBLEM:
----------------------------------------
>>     Also, when I have a (non-mac) cdrom in my SCSI CDROM drive and start
>>     up E/D 1.99o in Windows 95 Gold. Executor (-nosplash) runs but all I
>>     get is a black screen and I never see the browser or anything appear.
>>     So I have to kill that process and return to Windows 95. If I remove
>>     the CDROM from my drive executor then boots fine, althought the local
>>     drives still freeze it when I click on them.
>>
>>     Sean
>>
>>
>
>

JOSH VANAS WRITES THE REPLY:
----------------------------

I am no expert, but, have you tried installing MSCDEX as your CD-ROM driver?

Quote from the FAQ:

Executor accesses CD-ROMs through the Microsoft CD-ROM Extensions
(mscdex).  You need to have mscdex installed on your machine for Executor
to see your CD-ROM.  Furthermore, Executor is fussy and will not deal with
MS-DOS drives that contain Macintosh formatted media, unless the drive
letter is "J" or less.  If your CD-ROM drive letter is higher than J, you
will need to renumber it to be less than or equal to J.

Under Windows '95, there is a different way to access CD-ROMs -- a way
that Executor doesn't use.  However, Windows '95 can also use mscdex.  To
do so, you need to find and remove the:

rem - By Windows 95 Setup

portion from fthe mscdex line in your AUTOEXEC.BAT file.  You will also
need to edit your CONFIG.SYS file and make sure the CD-ROM driver is also
not commented out.



SEAN KANE WRITES IN REPLY TO JOSH VANAS' SOLUTION:
--------------------------------------------------

>     Yep, that's the problem. However, one would think It would just ignore
>     the cdrom if no MSCDEX was loaded not freak out. However this may be
>     to the fact that Windows95 assigns the cdrom a drive letter without
>     using mscdex and this is throwing executor for a loop......I will load
>     mscdex in my autoexec anyways to solve this......
>
>     One note: Loading mscdex, mouse drivers , etc into your autoexec will
>     slow down Win95 (although it shouldn't be noticable on a fast
>     machine). It forces Win95 into a "Compatibility Paging Mode" that
>     makes it work with unidentifable real-mode drivers, etc....
>
>     Sean
>


I hope that clears things up.  Sorry for any confusion.

        Josh