Hey guys I'm having a problem with my friends computer. It wont load up at all. Won't go into Windows XP, and it says there's a problem with the config.sys.

I made a bootdisk for her computer, then it says stating windows, the goes to the command prompt. From the command prompt I can only get to the A: and B:, which are exactly the same(I don't know why) and it CANT find the C: nor D: drive.

I tried a 98 boot disk, and I got a little further, but no luck.

I'm about to try a ME boot disk because when you start it up using the XP BD is says Mil edition. I found out that these files are corrupt:

ASPI4DOS.SYS
ASPI8US.SYS
ASPICD.SYS
RAMDRIVE.SYS
COMMAND.COM

Thanks for some help.

 

if u have xp cd boot from it. Should get u where u need to go

 

It won't read the C or D drives. Only the flopper.

 

have to set that up in the bios to boot from cd if its not doing it

 

We'll I'm in my thrid quarter at ITT Tech in Lake Mary, ironically enough, to learn how to fix these things when this happens. I have class tomorrow and I'll bring in the computer to see what can be done.

 

not sure if you got this fixed or not but as soon as you get past your POST (memory counting, etc) start hitting F8 you'll get the menu option and you can launch XP safe mode or XP recover console.

If you can't figure it out let me know...you can email me direct if you like.

Good Luck

Jim

 

From the little bit of info you posted it seems as though the ide controller on the motherboard is the problem.

Since you say neither the HD or cd-rom drive are being recognized this leads me to believe the ide controller is the culprit.

It may be disabled in the Bios although unlikely unless someone was playing in there.

If its an old computer could be that the ide controller failed. There may be two of them (primary and secondary). You can try using the secondary although this to is unlikely to work.

Best I can do from the info given.

 

freedom9ner,

You may be right but the thing that rules out the ide theory is the comment about "error in config.sys". Config.sys isn't seen until well after the post which recognizes the drives.

 

Punt Drop Kick

Then try it and see what happens


I tryed this onetime and it didn't work...

 

1. There is no need for config.sys in XP. It's a worthless file causing you no harm.
2. You need to be much more specific that "Won't go into XP". Sounds like some of my moron users...
3. Your 'boot disk' will can only see FAT-based volumes, and the NTFS volumes XP uses cannot be seen. Your CD cannot be seen since the drivers haven't been loaded and the PC cannot natively view the volume.
4. Never use a 95/98/ME disks with XP. Just run magnet over the PC, that's about what your doing.

Take the PC to a pro, your post and knowledge of PCs frightens me. Your doing more harm than good.

 

Now dzervit,

That isn't terribly nice. Grumpy I see.


What better way to learn than on a friend's computer.


Practice practice practice...

fdisk format install....repeat as needed.

 

I see we've got a senior helpdesk agent on the case now.... You'd better go ahead and escelate the ticket to a level 2...

 

dzervit is right about the non XP disks. They will not help but they also won't mess anything up unless you try to partition. As far as the CD-Rom not loading, the windows boot-up disks you used do load the drivers. Been a long time since messing with anything other then XP/ 2000 but I'm sure the drivers are loaded and you should see the CD-ROM as drive C. check your Bios to see what IDE devices are found. If no devices are detected then it is a motherboard or ide controller problem.

 

Actually, If the xp is loaded on a FAT partition then technically you can use a 98 boot disk to read the drive. Although little good would come out of it.

If he is getting any reference to config.sys which can be seen with XP corruption then you are long past worrying about the IDE detection or BIOS.

The system has obviously completly the drive detection, loaded the MBR and has looked to boot from the drive. There is an error in his XP configuration possibly boot.ini, the nt loader, etc.

It isn't likely a BIOS problem based on what is typed. However, what is typed is far from enough to truly figure out the problem.

 

This is why Dzervit is angry. He didn't like the last office reorganization.