Hi Everyone,
Have been trying to get past the blue screen and have been blocked. I have a floppy boot disk that wants- type name of the command interpreter- whatever I type in, it requests the command.

Can anyone get me past the blue screen, I can't ever read what is on the floppy disk.

I would appreciate your help getting the comp back to normal,

thanking you in advance,

frank

That most likely means you have a bad floppy - try making another on a fresh diskette

Same bluescreen issue as before?

We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

Report Offensive Follow Up For Removal

What is the STOP ERROR number at the bottom of your blue screen?

Computer Tech Support is a troubleshooter and toolbox for all your computer repair needs.

Hi JBoy,
nothing seems to work, I am looking at those boot disks put out by a number of companies. The boot disk made by the me os is not working, do you have any idea why I am getting this message about the command interpreter? I left a post about those boot disks and was told they were a waste of money. Your redirect diskette bombs out. The WME works well and then as if there was a time limit for how long it works without problems gets wacky and I have a cursing period aimed at gates and the m$ clan.

Thanks for hanging in there JBoy, I appreciate it, if you have any clues to the blue screen fits my comp has, I would give them a shot. I stay with it for a while and stop before my nerves kick in, then tackle the computer later on.

frank

... in WinME??

We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

Report Offensive Follow Up For Removal

OK - that was posted in response to the 'Stop Error' message (wrong forum, I suppose)

Anyhow - yes - I saw & responded to your question wrt bootdisks. I'm not sure that I understand you - there is no reason to purchase any kind of 'special' diskette, just download (& create) from the usual sources.

The error you've posted here regarding the command interpreter *usually* indicates a bad bootdisk - although a bad floppy drive or cable, or even bad RAM might produce that error as well.

When troubleshooting, you try and rule things out, so... "try another bootdisk" is the simplest test you can perform.

A bootdisk is a self contained version of DOS, so Windows problems will not affect it - either your bootdisk is bad, or you have a hardware issue (which may explain the bluescreen)

We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

Report Offensive Follow Up For Removal

Hello Curtis,
all I am getting is the prompt requesting the command interpreter with an example how to input it. I can't get to c drive and can't read the a drive. It boots up clean shows the ME logo, then shows system information fades and the blue screen comes up without the prompt. Everytime I boot up I get the feeling it's about to work because of the smoothness of the screen to screen, then the blue screen appears. Why it hangs up here, beat me, it was working well and then blue screen pops up. Many people do not like me, I have found the os very good (as well as m$ can put out something). Everything they put out have bugs, I found this os with the least amount of headaches, though it also has issues, but then again I guess it wouldn't be m$ without issues.

JBoy in your first post, the word diskette was underscored and I thought it was a trigger or redirect to a website, looking at your post again, I see it is this site that is uderscoring the word.

... don't sweat the small stuff? Those (double underlined, green) links are Intellitxt advertising, and a method of revenue for this site, for quite some time now (*years*).

Links posted by members will have the normal, single underline, and most of us avoid using green

Firefox users (such as myself) block such distractions with the excellent 'Adblock' extension (out of sight, out of mind)

Anyways, if you do intend to try and resolve this lengthy issue of yours, you need to see if you can boot to DOS successfully. If you can, then that would indicate a Windows issue - if you cannot (and have tried a series of different bootdisks) then you may believe the problem is associated with your hardware.

Determining which hardware component will also be a process of elimination

We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

Report Offensive Follow Up For Removal

Hi JBoy,
I just tried 4 boot disks plus the one I made from ME, the only one it recognizes is the one made off the os. The others have "disk error", remove and insert bootdisk. The one made off the os is the one with the-type the name of the command interpreter-. It goes no further than that, I tried a number starting with c:\windows\win and command, tried to get to c drive no luck. I have replaced the 4g hd that came with the unit with a 60g wd hd, it could only pick up 8g of the hd and reported an error possibly the remaining space on the hd. I had intentions of upgrading the bios since this unit was made in 98, my big problem here it is an acer bios, not one from mainstreams vendors. I suspect the bios is inferior to those found in other computer makers. I also see they have switched over to two mainstream bios suppliers. As to other hardware problems, it read the new hd so cable and drive is functioning, the ram was alright to the point of hd insertion and am out of clues as to what is blocking the unit from getting to the desktop.

Thanks for your help so far,

frank

Are you sure you have your BIOS configured to boot off the floppy 1st?

command interpreter = command.com

"it read the new hd so cable and drive is functioning"

.. which has nothing to do with the floppy drive, which is a separate cable, on a different controller.

As mentioned, make sure the system is set to boot from the floppy first (BIOS) - it may well be a bad floppy drive, cable or controller. As also previously mentioned, there is the possibility of bad RAM, which could well be the main issue, preventing any sort of boot device from functioning

Try to simplify things - you seem intent on complicating matters

We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

Report Offensive Follow Up For Removal

Hi Ham & JBoy,
the bios setoff is a, then c and then the cd.

I assume since the a drive and its system if giving me to separate readings from the floppy's, this sector is working. This is a guess on my part, but it would seem logical

One man's logic is another's lunacy

If the a: drive is set as the first boot device, then fine, we are inching towards some progress.

Troubleshooting time then - you've ruled out bad floppies, or so it would seem.

What next, I wonder?

We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true

Report Offensive Follow Up For Removal