cdrom thinks its F: not D:

well i just got told i used too many smilies in my post (i used 2) and im having to write it all out again but never mind eh?

this win 95 computer is convinced F: is the cdrom drive, D: is apparently just a thing that does nothing. i had to rename config.sys to .old so that i could get this thing running. when config.sys is there it mixes up all the drive letters and tells them they arent what they are. its very messed up.

D: is using real mode drivers so i downloaded the drivers needed and since then its just made things worse, they are the correct drivers they just dont do anything.

maybe this all sounds like garbage, but any help would be much appreciated.

 

The config.sys is not causing the drive letter mixup. That is only a DOS driver.

But by it not loading it does not allow the MSCDEX.EXE in the Autoexec.bat to work.

There may well be a line in the Autoexec.bat that is causing the problem by having an entry at the end of the MSCDEX.exe line.

It may have something like /L:F Which will set the CDROM to F:

And if all is well by not loading the Config.sys ( which I believe you are saying is true ) then I believe that may prove my thoughts.

Also you may want to check the DOSSTART.BAT for the same line.

BillyBob

 

i found one line in autoexec that was /L:G so i changed that to D: and put config back on and rebooted, made little difference.

it says in startup something like,

drive E: unit is TSYCD1
drive F: unit is CD003

at current without config.sys on my computer looks like this,

Floppy (A)
Win95 (C)
(D) drivespace says its a physical drive
(E)
(F) cdrom, although when i go into drivespace it doesnt exist
Host for e (G) - (dont ask)
Compressed (H)

whats up with that?

*never thought about smilies*

 

ok i checked dosstart.bat for the /L:G thing and low and behold there it was. so i changed it to and rebooted, but still nothing.

so i thought i might aswell show you what it says inside these files to see if you can spot the problem.

autoexec:


REM ======== ATAPI CD-ROM Install Modification - Begin ========
REM C:\DOS\MSCDEX.EXE /D:TSYCD1
C:\CDROMDRV\MSCDEX.EXE /D:TSYCD1 /D:CD003
REM ======== ATAPI CD-ROM Install Modification - End ========
@ECHO OFF
IF EXIST C:\RESETLOG.TXT DEL C:\RESETLOG.TXT > NUL
IF EXIST C:\FRUNLOG.TXT DEL C:\FRUNLOG.TXT > NUL
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;
REM LH C:\WINDOWS\COMMAND\MSCDEX /D:IDECD_00 /L
SET BLASTER=A220 I5 D1
@\AST_LOG
c:\windows\setupsa.exe
mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,c:\windows\COMMAND\keyboard.sys

REM LH C:\CDROM\MSCDEX /D:MSCD000

config:

REM DEVICEHIGH=C:\DEV\TSYCDROM.SYS /D:IDECD_00 /PS

DEVICEHIGH=C:\WINDOWS\COMMAND\DRVSPACE.SYS /MOVE

LASTDRIVE=Z
DEVICEHIGH=C:\CDROM\GSCDROM.SYS /D:MSCD000 /v

DEVICE=C:\TSY\TSYCDROM.SYS /D:TSYCD1

REM ======== ATAPI CD-ROM Install Modification - Begin ========
DEVICE=C:\CDROMDRV\ATAPICD.SYS /D:CD003
REM ======== ATAPI CD-ROM Install Modification - End ========

dosstart:

REM MSCDEX.EXE /D:OEMCD001 /L
REM MOUSE.EXE

LH C:\WINDOWS\COMMAND\MSCDEX /D:IDECD_00 /L
LH C:\DEV\MOUSE
CLS

i hope you can make sense out of it.

 

First off, windows does not need any drivers for the CD loading up from the Config.Sys and Autoexec.Bat files. It has it's own drivers for that.
Edit them to be like this:

Config.Sys

Dos=High,Umb
Device=C:\Windows\Himem.Sys
DEVICEHIGH=C:\WINDOWS\COMMAND\DRVSPACE.SYS /MOVE
REM DEVICEHIGH=C:\DEV\TSYCDROM.SYS /D:IDECD_00 /PS
rem DEVICEHIGH=C:\CDROM\GSCDROM.SYS /D:MSCD000 /v
rem DEVICE=C:\TSY\TSYCDROM.SYS /D:TSYCD1
REM ======== ATAPI CD-ROM Install Modification - Begin ========
rem DEVICE=C:\CDROMDRV\ATAPICD.SYS /D:CD003
REM ======== ATAPI CD-ROM Install Modification - End ========

You'll notice I added a couple of things to config.sys, they should be there and in that order.

Autoexec.bat

@ECHO OFF
REM ======== ATAPI CD-ROM Install Modification - Begin ========
REM C:\DOS\MSCDEX.EXE /D:TSYCD1
rem C:\CDROMDRV\MSCDEX.EXE /D:TSYCD1 /D:CD003
REM ======== ATAPI CD-ROM Install Modification - End ========
IF EXIST C:\RESETLOG.TXT DEL C:\RESETLOG.TXT > NUL
IF EXIST C:\FRUNLOG.TXT DEL C:\FRUNLOG.TXT > NUL
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;
REM LH C:\WINDOWS\COMMAND\MSCDEX /D:IDECD_00 /L
SET BLASTER=A220 I5 D1
@\AST_LOG
c:\windows\setupsa.exe
mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
mode con codepage select=850
rem keyb uk,,c:\windows\COMMAND\keyboard.sys
REM LH C:\CDROM\MSCDEX /D:MSCD000

With every line beginning with "rem ", nothing is done. This allows you to have these entries. I would have removed them completely but didn't want to freak you out.

 

about config, i left the common bit out cos i didnt think it wud need changing, are they the lines you added that you said i need?

im just gona try adding the bits that look different and see what happens. eek here goes.

lol @ /L i did that but then disabled smilies

edit:

well.. i've managed to compromise with this computer and set the cdrom to drive F. it was recognising two sets of drivers so i deleted the old ones, then i went into device manager and deleted the cdrom thing and when i rebooted it found the cdrom, and hey presto were running smoothly. or so i thought.

theres a disk i keep trying in it and it wont recognise it, but when it does which is about 1/5 attempts it thinks it an audio disk. i duno why so any help in that would be appreciated.

also, is there a way to delete drive D? drivespace recognises it as a physical drive but when i click it drivespace crashes.

 

I know someone will correct me if I am wrong and I expect them to please do so. It has been a LLLOONNGGG Time.

In other words HELP !!!!

Isn't Drivespace connected with DOS 6.22 drive compression to supposedly gain disk space ? And that is what created D: ?

And that is why D: is shown as a partition but it is also not meant to be used as a normal partition would be. And that is why it seems to crash when click on ?

Unless I thinking incorrectly that may well be the basis of the CDROM problem.

Me thinks Drivespace has ( or may have ) gone haywire. And this problem to be mainly on the DOS side of the House.

TheWoodster

You say you have a D: drive and the CDROM is F:. What happened to E: ?

BillyBob

 

From the Config.sys of the machine in question.

DEVICEHIGH=C:\WINDOWS\COMMAND\DRVSPACE.SYS /MOVE

In this case it would be DOS 7 not 6.22 but the same idea.

BB

 

E: is second hard disk we have in this. because i kept setting it D: and it wouldnt accept it, it would pick E: and make the hard disk a cdrom drive .. bloody thing. anyway. i found out the drivers i have for the cdrom actually dont work after all! the cdrom is so stone age (its a torisan cdrom cdr_s112) it wont work!

im thinkin of cannibalising another computer we have for the cdrom in that, but i will probably get killed for messing with it cos neither computer is mine

so what do i do with that drivespace move thing? delete?

 

I believe that is because D: is already asigned to Drivespace. Actuall I think D: is a hidden NON-DOS partition not useable by anything other than Drivespace.

I gotta wait for for someone else to confirm or deny that as a fact as it has been a long ( very long ) time since I messed with DOS and/or Win95.

In any case I now see why the CDROM would be F: and would be the correct letter.

BillyBob

 

yea i gotta run old school. no fair, i used to have a athlon 1700 but now i got 200 mmx

the owner of it is so proud of it for some reason i would most likely get thrown out if u tried to tinker. but sod it im gona anyway.

*i have to note, that all this faffing about is because of one measly game, shogun: total war!*

 

The parts I added was the first two lines.
The first I added Dos=High,Umb because you have a DeviceHigh command. The DeviceHigh command loads a program or device driver for dos in the Upper Memory Area, but first Dos must know it is to use it. However, this does not always mean the program or driver gets there. The second line [Himem.Sys] I added is because windows usually screams for it if not there, although Io.Sys will do this anyway without the existence of Config.Sys

BillyBob, I think you are right about DrvSpace.Sys, it is before 95. Win95 would use Drvspace.Bin, instead. I am sure you remember Drvspace.Bin and Dblspace.Bin located at C:\ in Win98SE. I disabled them from loading in my Msdos.Sys file and deleted them, just as well as they are useless with FAT32.

TheWoodster, I would REM the DrvSpace.Sys line in the Config.Sys, and let 95 use it's DrvSpace.Bin file. The existence of the old dos file in memory may be causing the crash when you try to access.

 

markp62

Dos=High,Umb
Device=C:\Windows\Himem.Sys

Aren't those two line reversed ?

Shouldn't it be ?

Device=C:\Windows\Himem.Sys
Dos=High,Umb

There is no high area until Himem is loaded.

BB

 

BillyBob, I have used it both ways, without noticing anything different. When I first came across a Dos OS able to use the Upper Memory Area [Dos 5.25], it stated in the M$ Dos manual that line should be first. We seemed to have dos files in use here, so just followed convection.
I also used to have a Win3.1 manual but it has disappeared. My first surprise with Win95 was no manual for it or dos, just the text files installed into C:\Windows.
But I do have it the Dos=High,Umb after my Himem in my current Config.Sys, following the logic it should be there.

 

i REM'd drvspace and i now i can actually do stuff with D: but, it keeps saying i need to format it, but i cant format it in drvspace so do it in explorer, but you cant format in explorer till its compressed in drvspace, but it wont compress until its formatted *breaks down and cries*. its not even a hard disk! i just want to delete it so i can assign F: back to D: but if im stuck with it it dont matter.

in config i have this now:

DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF
DEVICE=C:\WINDOWS\EMM386.EXE RAM

[COMMON]
FILES=60
BUFFERS=40
DOS=HIGH,UMB
shell=C:\COMMAND.COM C:\ /p /e:1024
device=c:\windows\COMMAND\display.sys con=(ega,,1)
Country=044,850,c:\windows\COMMAND\country.sys

 

According to this page, you would use this command at the dos prompt to delete the compressed drive;

drvspace /delete

or to format;

drvspace /format

 

well i tried drvspace /delete D: but it sed i had to specify the compressed volume file or summat example, drvspace.000 now there isnt one in D: because its not a physical drive. i think this computer needs putting down.

anyway thanks guys for all the help so far youve bin real helpful.

 

If you looked at the page I linked to, you would have seen these other commands that would help you on this;
drvspace /info
Displays information about the selected drive's free and used space, the name of its compressed volume file, and its actual and estimated compression
ratios.

drvspace /list
Lists and briefly describes all your computer's drives (except network drives and CD-ROM drives), and specfies whether DriveSpace's Automount and DoubleGuard features are enabled or disabled.

drvspace /format
Formats the selected compressed drive.

 

i tried the list thing and it came up with error, i tried the info thing and it sez i cant info D: i need to scandisk it but i cant scandisk until its formatted but i cant format and so on back to the loop.

its ******* really. i cant reload win 95 cos the pillock has none of the boot disks or anything needed. so it dont matter. D: will just have to stay there as .. well D:

 

I forgot just exactly how Drivespace works but I believe it has to be removed using the same software ( DOS ) that installed it.

I don't think you will be able to do anything with D: as it is a NON-DOS partition I believe.

I believe that is why you can not scandisk or Format it.

Also I believe ( guessing again ) that it is included in the MBR of the HD.

Now please remember that I may be just guessing as it has been a long,long time ( 20 years or more maybe ) since I got messed up with it ONCE. ANd that drove me to mutiple Hard drives.

BillyBob