|
-
January 27th, 2004, 04:30 AM
#1
Registered User
"Echo is on D" Error?
Hey Gang,
I received the below error when I recently installed my 2nd HD, my D drive. I copied and pasted some games and apps to my D drive. When I rebooted and came back after about 10 minutes this is what I saw:

I tried to re-label my D drive but I wasn't allowed to.
What is going on. I have scanned for viruses.
Thanks,
Orangeman
-
January 27th, 2004, 05:15 AM
#2
Geezer
I agree 'echo is on' sounds mighty suspicious ...
What does 'not allowed to' equal ? the message, if you recall ?
Whatever you scanned with use something else to confirm ...Try Hijack this too 
Any more info/developments ? There usually are when you are involved
-
January 27th, 2004, 05:51 AM
#3
Registered User
Here is a screenshot of what happened when I tried to rename it:

I am currently virus-scanning with Panda.
-
January 27th, 2004, 06:13 AM
#4
Intel Mod
"ECHO IS ON" is what DOS says to the ECHO command (as long as ECHO is on). How it would get into the Volume Label is another question, considering the start in life this drive had I wonder if the label is corrupted somehow.
Orangeman, as you have tried unsuccessfully to change the label from Windows, try going to a DOS prompt, type LABEL, and try to change the name, or at the prompt to give a name, simply press Enter to see if you can remove the existing label.
Sometimes you can do something from DOS that is not allowed for some reason in Windows.
Last edited by Platypus; January 27th, 2004 at 06:17 AM.
-
January 27th, 2004, 06:56 AM
#5
i just feel sorry for the drive ...full stop.
i remember years ago ,,playin a trick on the bosses computer ,,puttin the label command in the autoexec.bat ,,he renamed (to his dive) in windoze ,,,,when it rebooted the drive was named a rude word.
freddy
-
January 27th, 2004, 03:09 PM
#6
Registered User
check you autoexec.bat and rem out any cd device drivers
sound like something in dos a t start up caused this - due to ECHO ON being a common DOS command - and even more common for it to be the first line in the autoexec.bat
maybe something there is corrupted
HTH
-
January 27th, 2004, 03:23 PM
#7
Driver Terrier
Or its a nice little clue that you have a trojan.
-
January 27th, 2004, 03:50 PM
#8
Registered User
Actually what I did was use DiskWizard again from Seagate. I haven't tried to put anything on the new drive yet but It IS renamed to D.
Thanks again,
Orangeman
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks