What the hell is this?!


Recommended Posts

If you haven't done so already, I think you should definately run virus checks... also consider a government wipe of the drive and reformatting...

I have a fear of losing my data and therefore properly catalog and backup my data on a daily basis... If I ever have a problem of any sorts, it's an automatic format...

If you have so much music and do not want to risk losing it, I would take some extra precautions and reformat that drive

Link to comment
Share on other sites

FBI is on to you... that file is a FBI file that gets a list of all the music you have and sends it out to them, thats why you can get rid of it..

I would listen for sounds of a chopper and a bunch of cop cars outside of your house, if that happens, get rid of that drive... :D :D :shifty:

J/K.. I have no idea what that file is.. Hope you get rid of it...

Link to comment
Share on other sites

Few more sugestions I never saw mentioned, sorry if they were;

1. Run regedit or regedt32 and do a search for the file name. If it shows up, delete all references to it from within. (save the registry beforehand incase you can't reboot - although if you cannot reboot, try selecting "last known good configuration" from the startup options before you bother restoring the saved registry file.)

2. Try running a registry cleaner, I recommend Norton's WinDoctor as it has never done wrong by me.

3. Try using the right mouse button to drag it to the recycle bin. May sound silly but often works.

4. Turn on the option to "Delete items permanently" from the Recycle Bin properties, and then try to delete it.

Link to comment
Share on other sites

1. Make another folder for your mp3s.

2. Move (not copy), the mp3s from the old folder to the new folder, skipping the weird file.

3. Make sure all of them are indeed moved over and none have been left out.

4. Delete the old folder.

5. Create a folder with the same name of the one you just deleted, and move all your mp3s back. OR keep them in the other folder that you have moved them to.

Link to comment
Share on other sites

a nice low-level format will sort that bast*rd out for you :devil:

HeHe was waiting for someone to say that :)

Link to comment
Share on other sites

looking at that log file, something was definitely wrong, and probably still is. if you haven't already, run "chkdsk /r" and i think that should clean it up. as for a low level format, that's overkill. a quick format will get rid of it :laugh: but only do a quick format when you are formatting with the same filesystem as before, otherwise you'll have problems and should do a full format.

btw, for anyone who doesn't know, full format is not low level format. for a low level format you need special tools that should have come on floppies with your hard drive. hope you kept that documentation ;)

Link to comment
Share on other sites

Here are the steps that you have to take to delete it (trust me, it works):

1. Open the command prompt and keep it open

2. Open up Task Manager and kill the explorer.exe process

3. In command prompt, delete the file as suggested above (del filename*.*)

4. Go back to Task Manager and start a new process - Explorer.exe

5. Close the command prompt...

If you can't delete the file, you might have to move all of your mp3's and delete the folder itself...

Link to comment
Share on other sites

Yes, i just disabled it. The file is actually the gayest file ever.

rofl,

tell us when you get it fixed, I'm really curious to know wtf it is,

Do you have any idea how the hell it got there?

Link to comment
Share on other sites

I had a couple of files like this on my aunt's system, and I could not get them off I tried everything from wiping with about 4 different wiping programs and none worked. In the end I had to format the drive.

Looks to me like an error in the way Windows XP handles files 8.3 file names. Maybe you could try disabling 8.3 names temporarily, and then run chkdsk/r, to see if it cleans it up, then see if the file still exists. What I think happened is that it was file that got deleted but the corresponding 8.3 name did not get erased so you can't delete something that does not exist. Basically its a file system error.

EDIT: I just read your post and it does look like that was the problem this DA****.*** file is the 8.3 file name to the dave matthews song. Some how it got screwed up. try what I said and see if that works.

Link to comment
Share on other sites

I did a little more research on it and came up with this from a newsgroup. You may want to try it but, I take no credit or no responsibility for any damage done. So proceed with caution.

How to use wininit.exe and wininit.ini

http://support.microsoft.com/default.aspx?...B;en-us;q140570

http://members.aol.com/axcel216/newtip16.htm

Read and understand the above before continuing:

Make a note of the EXACT name and location of the file.

Example: C:\Windows\Temp\movie.mpg

Use Notepad, copy and paste the following (including the blank line),

(and substituting your files name and location), to a new text file.

[Rename]

NUL=C:\Windows\Temp\movie.mpg

Now save the file as: C:\Windows\wininit.ini

Shutdown and restart Windows. The file will

be deleted when Windows is restarted.

Warning: This deletes the file completely (bypassing the recycle bin),

so double-check everything!

Link to comment
Share on other sites

Nope didnt work, ive decided that i dont care anymore. Im going to let the bitch file live on my pc as long as it doesnt start any funny business and if it does... WHOOPASS

Link to comment
Share on other sites

Yup i tried it, the file doesnt actually seem to be a physical file, it appears to just be a ghost of a file that did exist so im not sure how tog et rid of it, essentially everytime i try to delete it i get told it doesnt exist so its sorta hard to gert rid of ;)

Link to comment
Share on other sites

pardon if this has been mentioned as i'd prefer not to look through 5 pages..

but have you tried booting to the xp cd, load the recovery console, then from the prompt, type chkdsk /r

its more thorough from the recovery console as no part of windows has loaded

Link to comment
Share on other sites

Follow the steps I have already mentioned, but delete the folder the file is in. Just move your mp3's out temporarily, then delete the directory itself from the command prompt. Then, just set it back up. Trust me, that will work.

Link to comment
Share on other sites

I cant, the folder can be moved but cant be deleted, ive already relocated the mp3s inside it and moved the folder somewhere ill never see it again.

Link to comment
Share on other sites

The plot thickens!!! I was looking to free up HD space and i went to D:\ and found this; its a log of my recent chkdisk 2 days ago. Can some tell me what its saying.

Checking file system on D:

The type of the file system is NTFS.

One of your disks needs to be checked for consistency. You

may cancel the disk check, but it is strongly recommended

that you continue.

Windows will now check the disk.

The record length 0x3 of attribute of type 0x30 and

instance tag 0x2 in file 0x10e6 is not aligned.

Truncating badly linked attribute records

from file record segment 4326.

The DOS file name attribute in file 0x10e6 is incorrect.

44 00 41 00 35 00 34 00 36 00 37 00 7e 00 31 00 D.A.5.4.6.7.~.1.

2e 00 03 00 4e 00 4b 00 63 00 6f 00 6f 00 0e 00 ....N.K.c.o.o...

0d 00 00 01 0e 00 5c 00 3f 00 3f 00 5c 00 56 00 ......\.?.?.\.V.

Correcting minor file name errors in file 4326.

Unable to locate the file name attribute of index entry DA5467~1.LNK

of index $I30 with parent 0x395 in file 0x10e6.

Deleting index entry DA5467~1.LNK in index $I30 of file 917.

Unable to locate the file name attribute of index entry Dave Matthews Band - Live 05.06.1999 - CD1.m3u.lnk

of index $I30 with parent 0x395 in file 0x10e6.

Deleting index entry Dave Matthews Band - Live 05.06.1999 - CD1.m3u.lnk in index $I30 of file 917.

Cleaning up minor inconsistencies on the drive.

CHKDSK is recovering lost files.

Recovering orphaned file DA5467~1.NK (4326) into directory file 917.

Cleaning up 55 unused index entries from index $SII of file 0x9.

Cleaning up 55 unused index entries from index $SDH of file 0x9.

Cleaning up 55 unused security descriptors.

Inserting data attribute into file 4326.

CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.

Internal Info:

4b 68 00 00 8f 19 00 00 43 2c 00 00 00 00 00 00 Kh......C,......

20 0c 00 00 00 00 00 00 69 00 00 00 00 00 00 00 .......i.......

60 63 35 02 00 00 00 00 90 f4 a9 09 00 00 00 00 `c5.............

90 f9 29 01 00 00 00 00 00 00 00 00 00 00 00 00 ..).............

00 00 00 00 00 00 00 00 90 10 be 14 00 00 00 00 ................

de 34 12 00 00 00 00 00 b8 17 00 00 00 00 00 00 .4..............

00 80 16 d3 04 00 00 00 cb 01 00 00 00 00 00 00 ................

Checking file system on D:

The type of the file system is NTFS.

A disk check has been scheduled.

Windows will now check the disk.

Cleaning up 2 unused index entries from index $SII of file 0x9.

Cleaning up 2 unused index entries from index $SDH of file 0x9.

Cleaning up 2 unused security descriptors.

CHKDSK is verifying file data (stage 4 of 5)...

File data verification completed.

CHKDSK is verifying free space (stage 5 of 5)...

Free space verification is complete.

i think that it is an index entry and that it is not ment to be deleted, or even ment for you to see it.

Link to comment
Share on other sites

Yup, it's an index entry. Like how Linux uses node files, that file is just the same for Windows. You can delete it if you want as it will be recreated normally later. But if you can't delete it, then that means that a few files are depending on it.

Also, it SHOULD be hidden, but for some reason it's visible to you... Weird.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.