Re-installing win.3.11 problem.
Brian
reinstall windows3.11 from original floppies.
During the set-up I get 'Windows set-up unable to read file WIN386.EXE
while copying 386 Enhanced Mode files.
Skipping this, the rest seems to install OK but on Boot up I have:
Starting MS-DOS
HIMEM is testing extended memory...
Finish up with a C prompt - Typing in WIN produces 'Cannot find
WIN386.EXE Needed to run in enhanced mode.
Some help would really be appreciated.
Brian.
---
This mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.281 / Virus Database: 149 - Release Date: 18/09/2001
Stephan Grossklass
>
> I have 486 computer. I have formatted the hard drive and tried to
> reinstall windows3.11 from original floppies.
> During the set-up I get 'Windows set-up unable to read file WIN386.EXE
> while copying 386 Enhanced Mode files.
> Skipping this, the rest seems to install OK but on Boot up I have:
> Starting MS-DOS
> HIMEM is testing extended memory...
> Finish up with a C prompt - Typing in WIN produces 'Cannot find
> WIN386.EXE Needed to run in enhanced mode.
> Some help would really be appreciated.
Could it be the Windows disk with win386.ex_ on it is defective? (Run
Scandisk or chkdsk on it.) If the file cannot be copied, 386 Enhanced
mode doesn't work either, of course, since the file is necessary for it.
Concerning "HIMEM is testing extended memory", all you have to do is to
add /TESTMEM:OFF to the line with himem.sys in config.sys. Probably
himem.sys was not used before, so Windows setup added an entry for it.
Stephan
--
Stephan Großklaß (7bit: Grossklass)
eMail: mailto:jgros...@t-online.de | Webmaster: http://www.i24.com/
Home: http://jgrossklass.bei.t-online.de/
P3-500, 128MB, 8+8+19GB HDD; MS-DOS 6.22, WfW 3.11, Calmira II 3.12
Artur Yelchishchev
<br...@mowbars.fsnet.co.uk> wrote:
>During the set-up I get 'Windows set-up unable to read file WIN386.EXE
>while copying 386 Enhanced Mode files.
Hi Brian,
In addition to Stephan's comments, you may use this method:
Go to the another PC, and try to copy "win386.ex_" file from
Windows distribution diskette to the another one (that is, copy
it to the other PC's hard disk, and then - to the another
diskette).
Next, copy this file from that second floppy to the your Win3.1
machine (to the c:\windows\system\ directory) and issue this
command:
'expand win386.ex_ win386.exe'
This should unpack the file.
It's known problem with floppy disks when particular floppy drive
is unable to read some files from given diskette due to the
head's misaligning or wear, while another drive may successfully
read it.
HTH,
Artur
Brian
Thanks for the reply Stephan...
I'm sure it's not a corrupted file on the floppy because I have two
sets of windows on floppies and both produce the same result.
So far, apart from running Scandisk and chkdsk at the C prompt I am
unable to go anywhere from that C Prompt. Then again,
I am not up to speed with the commands that would make things happen
from there.
Brian.
Brian
Hello Artur... Thanks too for the reply...
I can easily extract win386.exe from the windows floppy to another but
typing windows\system\directory at the C prompt just gets me a 'Bad
command or file name'
So, unsure how to get that file onto the PC's hard drive in order to
unpack it.
Brian.
Hi Brian,
'expand win386.ex_ win386.exe'
HTH,
Artur
Chia Ah Tee, Joseph
then enter
cd system.
Joseph Chia Ah Tee
Chia Ah Tee, Joseph
then format it.
Next install DOS and windows 3.11
Joseph Chia Ah Tee
-----Original Message-----
From: Brian [mailto:br...@mowbars.fsnet.co.uk]
Posted At: Friday, September 21, 2001 7:36 PM
Posted To: win3x
Conversation: Re-installing win.3.11 problem.
Artur Yelchishchev
<br...@mowbars.fsnet.co.uk> wrote:
>Sorry Artur... Think I sent this to you as an e-maill
No problem.
>Hello Artur... Thanks too for the reply...
You're welcome!
>I can easily extract win386.exe from the windows floppy to another but
>typing windows\system\directory at the C prompt just gets me a 'Bad
>command or file name'
Sure - it isn't correct DOS command.
>So, unsure how to get that file onto the PC's hard drive in order to
>unpack it.
You can either go to this directory by using "cd
c:\windows'system" command, or perform file copying directly,
using this command: "copy a:\win386.exe c:\windows\system"
Artur
Brian
Artur...
I have, on a floppy one file - WIN386.EXE 565KB Application which is
the perisher in question.
Attempting to copy from a to c using the command below gets me 'Sector
not found reading drive A'
Like there is nothing there?
This file I unzipped from a zip file sent to me... I failed to be able
to copy it from my floppies.
Brian.
>I can easily extract win386.exe from the windows floppy to another
but
>typing windows\system\directory at the C prompt just gets me a 'Bad
>command or file name'
Sure - it isn't correct DOS command.
>So, unsure how to get that file onto the PC's hard drive in order to
>unpack it.
You can either go to this directory by using "cd
c:\windows'system" command, or perform file copying directly,
using this command: "copy a:\win386.exe c:\windows\system"
Artur
Stephan Grossklass
>
> Artur...
> I have, on a floppy one file - WIN386.EXE 565KB Application which is
> the perisher in question.
> Attempting to copy from a to c using the command below gets me 'Sector
> not found reading drive A'
This may mean that the floppy drive is set up incorrectly (1.44 MB 3.5"
as 1.2 MB 5.25", for example); check the BIOS setup to ensure that the
drive type matches the drive installed.
BTW: If Outlook Express refuses to quote correctly, I'd set the quote
characters manually.
Artur Yelchishchev
<br...@mowbars.fsnet.co.uk> wrote:
>Attempting to copy from a to c using the command below gets me 'Sector
>not found reading drive A'
>Like there is nothing there?
Hi Brian,
Have you tried another diskette? As you've said _most_ of your
Win3.1 floppies are working Ok, I think it's all right with CMOS
floppy drive settings, but you may re-check it, too.
Also, you may try to format floppy diskette on your "to be
Win3.1" machine ('format a: /u' at DOS prompt), then copy
required file from another PC and transfer it to the problematic
one.
Artur
Brian
Eureka!!! Some considerable success! Win 3.11 now up and
running - Got the Program manager OK.
er... Dare I push my luck now and ask how I might get the 'D'
partition back so that I can get the CD ROM installed?
Thanks for your patience... Great moment when Windows ran this
morning!
Brian.
>Attempting to copy from a to c using the command below gets me
'Sector
>not found reading drive A'
>Like there is nothing there?
Hi Brian,
Have you tried another diskette? As you've said _most_ of your
Win3.1 floppies are working Ok, I think it's all right with CMOS
floppy drive settings, but you may re-check it, too.
Also, you may try to format floppy diskette on your "to be
Win3.1" machine ('format a: /u' at DOS prompt), then copy
required file from another PC and transfer it to the problematic
one.
Artur
Stephan Grossklass
>
> Eureka!!! Some considerable success! Win 3.11 now up and
> running - Got the Program manager OK.
> er... Dare I push my luck now and ask how I might get the 'D'
> partition back so that I can get the CD ROM installed?
'D' is not a partition on the hard drive in this case ('partition' only
applies to hard drives), but simple another drive. Installing a CD-ROM
drive in DOS and Win 3.1 is pretty simple:
In config.sys one should find a line similar to this (after himem.sys,
emm386.exe and dos=high,umb):
device[high]=c:\somepath\cdromdrv.sys /D:MSCD001
rem where cdromdrv.sys is the driver for the CD-ROM drive; look
rem on the mfr's website or the floppy disk that came with the drive
In autoexec.bat the following line should be included:
[LH ]C:\somepath\MSCDEX.EXE /D:MSCD001
rem MSCDEX should be ver. 2.23 or newer; Smartdrv (>=5.0) should
rem be loaded after it to ensure that the CD-ROM drive is cached.
Brian
Yikes! Stephan... Am I ever glad you didn't send me the complicated
way!
Sorry, but that is all way over my head, can't even find my way into
config.sys.
No problem having a go at the system files if I can get at them, but
will need an approach more suited to my very limited knowledge.
Brian.
'D' is not a partition on the hard drive in this case ('partition'
only
applies to hard drives), but simple another drive. Installing a CD-ROM
drive in DOS and Win 3.1 is pretty simple:
In config.sys one should find a line similar to this (after himem.sys,
emm386.exe and dos=high,umb):
device[high]=c:\somepath\cdromdrv.sys /D:MSCD001
rem where cdromdrv.sys is the driver for the CD-ROM drive; look
rem on the mfr's website or the floppy disk that came with the drive
In autoexec.bat the following line should be included:
[LH ]C:\somepath\MSCDEX.EXE /D:MSCD001
rem MSCDEX should be ver. 2.23 or newer; Smartdrv (>=5.0) should
rem be loaded after it to ensure that the CD-ROM drive is cached.
Stephan
--
Stephan Großklaß (7bit: Grossklass)
eMail: mailto:jgros...@t-online.de | Webmaster: http://www.i24.com/
Home: http://jgrossklass.bei.t-online.de/
P3-500, 128MB, 8+8+19GB HDD; MS-DOS 6.22, WfW 3.11, Calmira II 3.12
John Dulak
>
> Yikes! Stephan... Am I ever glad you didn't send me the complicated
> way!
> Sorry, but that is all way over my head, can't even find my way into
> config.sys.
> No problem having a go at the system files if I can get at them, but
> will need an approach more suited to my very limited knowledge.
>
> Brian.
Brian:
You can edit the CONFIG.SYS and AUTOEXEC.BAT files from the DOS comand
line using the EDIT command or from Windows using NOTEPAD. Both files
are located in the "root' direstory of your C: drive. The Formal path to
each is;
C:\CONFIG.SYS
C:\AUTOEXEC.BAT
Remember to SAVE the files after you modify them. You will also have to
reboot the computer before any changes you made will take effect.
As to WHAT has to be done to get access to the CD drive, the following
is a summary. You may already have a copy of MSCDEX.EXE. To find out,
type the following line at any DOS prompt;
dir c:\mscdex.exe /s <enter>
This will search yuor entire C: dirve for the file MSCDEX.EXE and report
it's location.
Assuming your CD-ROM drive uses an IDE interface and NOT a SCSI
interface, in your CONFIG.SYS file, you need to have a line
something like:
DEVICE=C:\CDROM\MTMCDAI.SYS /D:MSCD001
Where "MTMCDAI.SYS" is the CD-ROM driver file for your CD-ROM
drive and "C:\CDROM" is the drive and directory where it is located.
The "/D:" switch defines an arbitrary descriptor (MSCD001) that is
passed
to MSCDEX.EXE in your AUTOEXEC.BAT file. (See Below)
A collection of "generic" IDE CD-ROM drivers along with
sample CONFIG.SYS and AUTOEXEX.BAT files can be found in
this self extracting archive:
http://www.bootdisk.com/genfiles/thepatch.exe
A selection of IDE CD-ROM drivers is available here:
http://www.driverguide.com/archives/archive1/41.html
** AND ** in your AUTOEXEC.BAT file you need to have a line
something like:
C:\CDROM\MSCDEX.EXE /D:MSCD001 /L:I
Use the proper path to access MSCDEX.EXE it may be located in
C:\DOS\ OR C:\WINDOWS\ or a directory created by the CD-ROM
install program. You can also download it at:
ftp://ftp.microsoft.com/softlib/MSCDX223.EXE
* The "/L:" switch lets you explicitly specify the CD-ROM Drive Letter.
* The string following the /D: statement must _EXACTLY_ match the
string in CONFIG.SYS following your CD-ROM device driver.
* If your CONFIG.SYS file contains a "LASTDRIVE=*" line be sure "*" is
at least one letter higher in the alphabet than your last drive or
equal to the letter used in the /L: switch.
Hope this helps.
John
--
\\\\\//
"Don't take life so seriously... | |
...it's only a temporary condition." (.) (.)
========================================oOO==(_)==OOo==
________________________________
| John G. Dulak |
| Gnomeway Services |
/)| jdu...@telerama.com |(\
/ )|http://www.telerama.com/~jdulak |( \
_( (|________________________________|) )_
((( \ \ > /_) ( \ < / / )))
(\\\ \ \_/ / \ \_/ / ///)
\ / \ /
\ _/ \_ /
/ / \ \
Brian
Null... If only I had known how to do that... C:\Windows\System
produced nothing but Bad command message.
In a moment of absolute frustration I foolishly attempted to setup
some CD-ROM drivers that I got from the manufacturers web site.
This was not a good idea... I am now back to square one.. A straight
boot produces: IDE/ATAPI CD-ROM Device driver Version 2.11 17.30.39
06/07/96 CD-ROM drive #0 found on 170h port slave device, V1.18. I
can then go no further, just a flashing cursor.
Starting with a win95 SAtartup disk takes me to an 'A' prompt -
Changing it to C only produces the dreaded Bad command or file name
message..
Nothing left now but the river!!!
Brian.
Brian, if you'll send me a copy of your autoexec.bat and config.sys
files I'll make the changes for you and send them back. When I do
I'll also send a generic CD ROM driver (oakcdrom.sys) that you can
copy to your C:\Windows\System directory. This driver has worked with
every CD drive I've ever tried.
Just an offer .......
Stephan Grossklass
>
> Null... If only I had known how to do that... C:\Windows\System
> produced nothing but Bad command message.
Of course it does - C:\Windows\System is a *directory*, not an
executable or driver file. The entry in config.sys would have been:
device=c:\windows\system\oakcdrom.sys /D:MCD001
BTW: You do not happen to have a library near you? A good book about DOS
basics would really be helpful.
> In a moment of absolute frustration I foolishly attempted to setup
> some CD-ROM drivers that I got from the manufacturers web site.
> This was not a good idea... I am now back to square one.. A straight
> boot produces: IDE/ATAPI CD-ROM Device driver Version 2.11 17.30.39
> 06/07/96 CD-ROM drive #0 found on 170h port slave device, V1.18. I
> can then go no further, just a flashing cursor.
This sounds familiar - many modern drivers apparently need a PCI IDE
controller and don't work with old ISA stuff (resulting in the hangup
you described). A driver that does is Mitsumi's mtmcdai.sys. To solve
your problem, press <F8> when DOS starts booting, then SKIP the line
with the mfr's CD-ROM driver in it. Then download Mitsumi's driver
(prereferably an older one [I'm not sure whether the newest version will
still work], use ftpsearch.lycos.com to locate a copy of mtmcdai.sys
that's from 1997 or older) and copy it to the computer's hard drive.
Once this is done, you should (a) tell us where mtmcdai.sys and
mcdex.exe are located on the hard drive and (b) post the contents of
config.sys and autoexec.bat here. Otherwise you'll just get an even
bigger mess.
Brian
Stephan..
I have located mtmcdai.sys (1995) and copied it to the win3.11 system
file and am able to run 3.11 by bypassing the CD-ROm driver line.
Please forgive my stupidity but I have to ask how I find where the two
files are that you asked about also how do I find and copy the files
config.sys and autoexec.bat to a floppy.
I understand your annoyance with my ignorance of DOS basics but I
would, at my age, stand as much chance learning that as I would an
advanced course in Particle Physics. The computer I am using for
this has ME on it, DOS has never been part of computing for me I'm
afraid, hence my request for assistance.
Thanks once again for all your patience..
Brian.
Brian
Brian.
AUTOEXEC.BAT
C:\DOS\SMARTDRV.EXE /X
@ ECHO OFF
PROMPT SpSg
PATH C:\WINDOWS;C:\DOS
SET TEMP=C:\DOS
MODE CON CODEPAGE PREPARE=((437) C:\DOS\EGA CPI)
MODE CON CODEPAGE SELECT=437
KEYB UK,, C:\DOS\KEYBOARD.SYS
MSCDEX /D:MSCD001 /V
CONFIG.SYS
DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\WINDOWS\HIMEM.SYS
DOS=HIGH
COUNTRY=044,,C:\DOS\COUNTRY.SYS
DEVICE=C:\DOS\DISPLAY.SYS CON=(EGA,,1)
FILES=30
DEVICE=C:\WINDOWS\IFSHLP.SYS
STACKS=9,256
DEVICE=C:\CDROM\MTMCDAI.SYS ID:MSCD001
Brian, if you'll send me a copy of your autoexec.bat and config.sys
files I'll make the changes for you and send them back. When I do
I'll also send a generic CD ROM driver (oakcdrom.sys) that you can
copy to your C:\Windows\System directory. This driver has worked with
every CD drive I've ever tried.
Just an offer .......
On Sun, 23 Sep 2001 13:38:29 +0100, "Brian"
<br...@mowbars.fsnet.co.uk> wrote:
Stephan Grossklass
>
> AUTOEXEC.BAT
>
> C:\DOS\SMARTDRV.EXE /X
> @ ECHO OFF
> PROMPT SpSg
> PATH C:\WINDOWS;C:\DOS
> SET TEMP=C:\DOS
> MODE CON CODEPAGE PREPARE=((437) C:\DOS\EGA CPI)
> MODE CON CODEPAGE SELECT=437
> KEYB UK,, C:\DOS\KEYBOARD.SYS
> MSCDEX /D:MSCD001 /V
Changs that to:
@ ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;C:\DOS
SET TEMP=C:\TEMP
:: You must create the directory c:\temp, of course - putting temporary
:: files into the DOS directory is not a particularly good idea, but
:: the default setting
:: MODE CON CODEPAGE PREPARE=((437) C:\DOS\EGA CPI)
:: MODE CON CODEPAGE SELECT=437
loadhigh KEYB UK,, C:\DOS\KEYBOARD.SYS
lh C:\DOS\MSCDEX /D:MSCD001 /V
C:\DOS\SMARTDRV.EXE /X
lh doskey /insert
CONFIG.SYS
DOS=HIGH,UMB
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE noEMS
DEVICEHIGH=C:\DOS\SETVER.EXE
COUNTRY=044,,C:\DOS\COUNTRY.SYS
rem DEVICE=C:\DOS\DISPLAY.SYS CON=(EGA,,1)
FILES=30
DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS
STACKS=9,256
DEVICEHIGH=C:\CDROM\MTMCDAI.SYS /D:MSCD001
Assuming that all files do indeed exist in the places specified (i.e.
there should be a directory 'CDROM' on C: with mtmcdai.sys in it, and
you should create the c:\temp directory), this should give you more
conventional memory and a working CD-ROM drive. You *may* need to use
another version of mscdex.exe if yours is older than 2.23 (run mscdex on
the command prompt, this will give you a message "MSCDEX version x.xx is
already installed"); 2.21 couldn't read some CDs.
Brian
Good Morning Stephan.
I have created a c:\temp directory and a CDROM directory and put the
mtmcdai.sys into that.
I have carefully made the changes listed below.
On boot up I recieve the following messages:
Bad or missing C:\CDROM\MTMCDAI.SYS
error in CONFIG.SYS line 9
MODE prepare code page function completed
MODE select code page function completed
Device driver not found: `MSCD001`
No valid CDROM device drivers selected.
I am also now having a problem as,using the windows MS-DOS Editor I go
File/Open and enter C:\WINDOWS\CONFIG.WIN (or SYS)
and all I do is get that line on the screen, it won't open the
config.win (or sys) file.
As soon as I can find a library in this very small town of ours I'll
go get a book on DOS - Promise!
Brian.
"Stephan Grossklass" <sgrossklas...@my-deja.com> wrote in
message news:9onl2h$vfq$03$1...@news.t-online.com...
Changs that to:
CONFIG.SYS
Brian
Gets the same result...
Edit you files from a DOS prompt by typing "edit config.sys" or "edit
autoexec.bat" at the root directory (which is "C:\")
To save (my way anyhow) === CNTL, "F", "S"
To exit (again the way I do it) === CNTL, "F", "X"
Brian
Can't, in Search, find either of those but I entered second one as the
last line starting with DEVICE=C....
That means the C:\CDROM\MTMCDAI.SYS file is not being found. Try to
do a seach for it and point to the correct directory.
Also make sure it reads:
C:\CDROM\MTMCDAI.SYS /D:MSCD001
Brian
Null...
Made correction to config.sys
I have the oakcdrom.sys file which I have copied to c:\cdrom
I have changed the line in config.sys to DEVICE=C:\CDROM\OAKCDROM.SYS
/D:MSCD001
Bootup gives me this:
This driver is provided by Oak Technologies, Inc.,
OTI-91X ATAPI cd-rom device driver, Rev D91XV352
(c) copyright Oak technologies Inc 1987 - 1997
Device name : MSCD001
No drives found, aborting installation
Code page operation not supported on this device
Device error during select
Device driver not found: `MSCD001`
Device driver not found: `MSCD001`
No valid CDROM device driver found
I downloaded updated drivers for this CD from the manufacturers web
site which included 33 files (inc oakcdrom.sys)
Should these be installed somewhere?
Regards,
Brian.
<br...@mowbars.fsnet.co.uk> wrote:
>Hello Null...May I take you up on that offer?
>Brian.
>
>AUTOEXEC.BAT
>
>C:\DOS\SMARTDRV.EXE /X
>@ ECHO OFF
>PROMPT SpSg
>PATH C:\WINDOWS;C:\DOS
>SET TEMP=C:\DOS
>MODE CON CODEPAGE PREPARE=((437) C:\DOS\EGA CPI)
>MODE CON CODEPAGE SELECT=437
>KEYB UK,, C:\DOS\KEYBOARD.SYS
>MSCDEX /D:MSCD001 /V
Based on one entry in your config.sys file (below) it appears as
though you have Windows For Workgroups (WFWG) installed. I base this
on the fact that there is an "ifshlp.sys" entry which is not installed
under Windows 3.1.
There's an error on the MSCDEX line of your autoexec.bat file. The
last line should read:
C:\DOS\MSCDEX /D:MSCD001 /D:MSCD001
In addition I suggest you check two things regarding the mscdex file:
(1) Look in *both* the C:\DOS directory and C:\Windows directory for
an "mscdex.exe" file and record the file date.
(1.a) If you're using DOS 6.22 the date of this file in the DOS
directory will be 5/31/1994.
(2) Change the mscdex line to use the most recent file (newest date)
by entering either (a) "C:\DOS\MSCDEX /D:MSCD001 /D:MSCD001" -or-
"C:\WINDOWS\MSCDEX /D:MSCD001 /D:MSCD001" (you'll notice I left off
the "/V" because all it does is disply memory statistics when it
starts and that doesn't really matter in most cases).
>CONFIG.SYS
>
>DEVICE=C:\DOS\SETVER.EXE
>DEVICE=C:\WINDOWS\HIMEM.SYS
>DOS=HIGH
>COUNTRY=044,,C:\DOS\COUNTRY.SYS
>DEVICE=C:\DOS\DISPLAY.SYS CON=(EGA,,1)
>FILES=30
>DEVICE=C:\WINDOWS\IFSHLP.SYS
>STACKS=9,256
>DEVICE=C:\CDROM\MTMCDAI.SYS ID:MSCD001
The last line of your config.sys file has an error:
At present it reads: DEVICE=C:\CDROM\MTMCDAI.SYS ID:MSCD001
It should read: DEVICE=C:\CDROM\MTMCDAI.SYS /D:MSCD001
(note the forward-slash just before the "D", not an "I").
COMMENT: Use the "oakcdrom.sys" file (41KB attached to this message)
instead of the mtmcdai.sys you're currently using if you still cannot
access your CD drive after making the changes outlined above.
If you need to, you do this by copying the oakcdrom.sys file
(attached) to your C:\CDROM directory and change the last line of your
config.sys file to read: DEVICE=C:\CDROM\OAKCDROM.SYS /D:MSCD001 then
reboot your system and it should see your CD.
To add further confusion, I've attached the config.sys and
autoexec.bat files that I use on my Win 3.1 system. They're a lot
more complex than what you're using but should give you and idea of
what's possible as you progress through the learning phase.
Remember that from a "DOS" prompt you can enter "help" and get a list
of various commands with a detailed breakdown of their use and syntax.
NOTE TO NG: If attachments are forbidden my apologies, I couldn't
find a FAQ or Charter for this newsgroup outlining the rules.
Stephan Grossklass
>
> Null...
> Made correction to config.sys
> I have the oakcdrom.sys file which I have copied to c:\cdrom
> I have changed the line in config.sys to DEVICE=C:\CDROM\OAKCDROM.SYS
> /D:MSCD001
>
> Bootup gives me this:
> This driver is provided by Oak Technologies, Inc.,
> OTI-91X ATAPI cd-rom device driver, Rev D91XV352
> (c) copyright Oak technologies Inc 1987 - 1997
> Device name : MSCD001
> No drives found, aborting installation
This means that the CD-ROM driver did not detect any drive. What happens
if you use mtmcdai.sys instead of oakcdrom.sys? If that doesn't work
either, I'd suspect incorrect installation of the drive (i.e. not
jumpered or connected correctly).
> Code page operation not supported on this device
> Device error during select
You didn't REM out the MODE CON CODEPAGE stuff.
> Device driver not found: `MSCD001`
> Device driver not found: `MSCD001`
> No valid CDROM device driver found
If the CD-ROM driver doesn't load because it can't find any drive,
MSCDEX will complain, of course. The error about the device driver not
being found should *not* appear twice BTW - strange.
> I downloaded updated drivers for this CD from the manufacturers web
> site which included 33 files (inc oakcdrom.sys)
> Should these be installed somewhere?
You don't need more than the driver itself and possibly MSCDEX.
Bill Marcum
Brian wrote in message <9orpq8$qd7$1...@news8.svr.pol.co.uk>...
>I downloaded updated drivers for this CD from the manufacturers web
>site which included 33 files (inc oakcdrom.sys)
>Should these be installed somewhere?
>
>Regards,
>Brian.
>
Brian
Just a readme.txt which refers to help for windowsME problems.
Sort of stuck now... Still no CD-ROM - No idea where to go from
here...
Brian.
"Bill Marcum" <bma...@iglou.com> wrote in message
news:3bb23...@news.iglou.com...
---
ted.f...@virgin.net
You could go to look in the yellow pages( your in the UK) and see if
theres a small , read one man band pc repairer in your area. Weve
several in my area Bmth Poole. they will sort it for you for a nominal
sum.Ted frater.
you need a man who can.
Brian
Thanks for that helpful advice, but I'll keep trying. You could do
with some help with your grammar.
Jay T. Blocksom
Null <nu...@anyonlinenetorggovcomthateverexisted.net> wrote:
>
> From: Null <nu...@anyonlinenetorggovcomthateverexisted.net>
> Newsgroups: comp.os.ms-windows.setup.win3x
> Subject: Re: Null..config.sys and autoexec.bat files (here are the
> corrections).. (1/1)
> Message-ID: <7l21rtgekntigqd36...@4ax.com>
> Lines: 1018
> X-Complaints-To: ab...@usenetserver.com
> NNTP-Posting-Date: Tue, 25 Sep 2001 09:39:23 EDT
> Organization: BELLSOUTH.net
> Date: Tue, 25 Sep 2001 09:46:15 -0400
>
>
> begin 644 AUTOEXEC.BAT
> M0$5#2$\@3T9�I`0TQ3#0IG;W1O("5C;VYF:6<E#0H-"@T*.DU/5$A%4@T*
> M0SI<445-35Q,3T%$2$D@+U(Z,R!#.EQ724Y$3U=37%--05)41%)6+D5810T*
> M0$5#2$\@3T9�I04D]-4%0@)'`D9PT*4$%42"!#.EQ114U-.T,Z7$-,05))
[snip]
And exactly where did you see the word "binary" in the name of this
newsgroup?
-- Jay T. Blocksom
----------------------------
Appropriate Technology, Inc.
approtek[at]rcn.com
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NOTE: E-Mail address in "From:" line is INVALID! Remove +SPAMBLOCK to mail.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Unsolicited advertising sent to this E-Mail address is expressly prohibited
under USC Title 47, Section 227. Violators are subject to charge of up to
$1,500 per incident or treble actual costs, whichever is greater.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Stephan Grossklass
>
> On Tue, 25 Sep 2001 09:46:15 -0400, in <comp.os.ms-windows.setup.win3x>,
> Null <nu...@anyonlinenetorggovcomthateverexisted.net> wrote:
> >
> > begin 644 AUTOEXEC.BAT
> > M0$5#2$\@3T9�I`0TQ3#0IG;W1O("5C;VYF:6<E#0H-"@T*.DU/5$A%4@T*
> > M0SI<445-35Q,3T%$2$D@+U(Z,R!#.EQ724Y$3U=37%--05)41%)6+D5810T*
> > M0$5#2$\@3T9�I04D]-4%0@)'`D9PT*4$%42"!#.EQ114U-.T,Z7$-,05))
> [snip]
>
> And exactly where did you see the word "binary" in the name of this
> newsgroup?
What, your news server doesn't use Cleanfeed? :) (I don't even *see* the
article here.)