It is currently Tue Oct 20, 2026 4:49 pm


msdos compatability mode

All computer hardware support

msdos compatability mode

Postby GinSlinger » Tue Sep 16, 2003 9:48 pm

hey Gecko...

My HDD is using msdos compatability mode....and I cant seem to get it to do elsewise! there are no specs on the drive itself so I cant even enter sectors, etc in BIOS to try to get windows to recognize the dang thing.
Umm...any advice?

rig specs:
win 98SE
PIII 800 EB
KT-7 Raid mobo
20 Gig Western Dig
SBLive Platinum
GF2
512 Megs PC133
User avatar
GinSlinger
Newbie
Newbie
 
Posts: 6
Joined: Wed Sep 17, 2003 1:00 am
Location: Sin City, Nevada

Thanks given:0
Thanks received:0
Top

Postby Restek » Tue Sep 16, 2003 10:14 pm

Can you send me a private message with copies of the files 'autoexec.bat' and 'config.sys' ? They will be found in your c:\ drive.
User avatar
Restek
Geek Alumni
 
Posts: 1002
Joined: Tue Sep 18, 2001 1:00 am
Location: Uk

Thanks given:0
Thanks received:0
Top

Postby GinSlinger » Tue Sep 16, 2003 11:45 pm

ok Restek...info sent.

And thanks in advance for the assistance!!!

-Gin
User avatar
GinSlinger
Newbie
Newbie
 
Posts: 6
Joined: Wed Sep 17, 2003 1:00 am
Location: Sin City, Nevada

Thanks given:0
Thanks received:0
Top

Postby Restek » Wed Sep 17, 2003 1:32 pm

OK - I've had a look at the files you sent me. They appear to be the default ones that are found on a windows 98/ME boot floppy disk, but it is unusual to have these as the boot files for your hard disk installed version of windows. Did these files definitely come from your c:\ directory? When you boot the PC, does it give a menu with the options 'start with CDROM support' 'start without CDROM support' and 'help'?

If the above 2 questions are TRUE, then as a troubleshooting step can you do this:
First of all, if you haven't already got one, make sure you have created a windows rescue disk (go to start menu -> settings -> control panel -> add/remove hardware -> rescue disk tab and click on 'create disk' (you'll need a spare floppy disk). This is just a precautionary step incase anything goes wrong.

Then, rename 2 files. Rename autoexec.bat to auto.bat and config.sys to conf.sys. Reboot, and see if your drives are still in compatability mode.

If for any reason you cannot reboot after renaming those 2 files, boot off the rescue disk & type these commands at the a:\> prompt (pressing enter after each one):
ren conf.sys config.sys
ren auto.bat autoexec.bat

This will rename the files back to their original names :)
User avatar
Restek
Geek Alumni
 
Posts: 1002
Joined: Tue Sep 18, 2001 1:00 am
Location: Uk

Thanks given:0
Thanks received:0
Top

Postby Ranger Bob » Wed Sep 17, 2003 2:14 pm

Take a look at this MSKB article to see if it helps:

Image

User avatar
Ranger Bob
Geek Alumni
 
Posts: 550
Joined: Fri Sep 12, 2003 1:00 am
Location: Florida

Thanks given:0
Thanks received:0
Top

Postby GinSlinger » Wed Sep 17, 2003 8:58 pm

Restek....the filepath to the files I sent ya was C:\windows\command\ebd...

If there is another location where there should be an instance of these files, I don't know of it.

I'm gonna try yer suggestions....thanks much and I will post results asap.

-Gin
You can run, but you'll only die tired!
User avatar
GinSlinger
Newbie
Newbie
 
Posts: 6
Joined: Wed Sep 17, 2003 1:00 am
Location: Sin City, Nevada

Thanks given:0
Thanks received:0
Top

Postby Restek » Thu Sep 18, 2003 7:09 pm

OK - you need to send me the ones found in c:\ (or alternatively carry out the procedures I mentioned above on the ones in c:\ ), not on these ones :)

You may need to go to folder options on the 'tools' menu of windows explorer and select 'show hidden folders', and turn OFF 'hide protected system files' in order to see the files :)
User avatar
Restek
Geek Alumni
 
Posts: 1002
Joined: Tue Sep 18, 2001 1:00 am
Location: Uk

Thanks given:0
Thanks received:0
Top

Postby Restek » Fri Sep 19, 2003 12:14 pm

Well, I had a look at the correct files - they are about as minimal as they come with nothing out of the ordinary there atall, so don't bother trying the renaming trick - it'll not do any good in this scenario. Bit of a shame really - I was banking on there being something in those files that was causing this :)

Next option is to load the chipset drivers for your motherboard. I believe the KT7 uses and via chipset, so head over to www.viaarena.com and download the 'hyperion 4-in-1' drivers. Install them and see if it helps :)
User avatar
Restek
Geek Alumni
 
Posts: 1002
Joined: Tue Sep 18, 2001 1:00 am
Location: Uk

Thanks given:0
Thanks received:0
Top

Postby Gecko » Fri Sep 19, 2003 2:41 pm

Have you tried using the Data Lifeguard Tools ver 10.0 from ?
It will test your drive for problems and errors, fixes certain errors, scans for bad sectors, run a BIOS check on drives detected and provides drive information (serial and model number). From the serial and model number information you can get the Cylinders, Heads, Sectors/Track and Jumper Setting Information from
User avatar
Gecko
Super Moderator
Super Moderator
 
Posts: 5209
Joined: Thu Oct 25, 2001 1:00 am
Location: Florida, USA

Thanks given:1
Thanks received:23
Top

Postby GinSlinger » Sun Sep 21, 2003 11:27 pm

fantastic guys!! Thank you for all the info!

now I shall go see if any of it fixes the problem....but I gotta tell ya I think one or the other has to...

one more biiiiig thanks and I'm off to fix me a HDD!

-Gin
You can run, but you'll only die tired!
User avatar
GinSlinger
Newbie
Newbie
 
Posts: 6
Joined: Wed Sep 17, 2003 1:00 am
Location: Sin City, Nevada

Thanks given:0
Thanks received:0
Top


Return to Hardware

Who is online

Users browsing this forum: No registered users and 7 guests

cron