Register | Login
Views: 19364387
Main | Memberlist | Active users | ACS | Commons | Calendar | Online users
Ranks | FAQ | Color Chart | Photo album | IRC Chat
11-02-05 12:59 PM
0 user currently in Hardware/Software.
Acmlm's Board - I2 Archive - Hardware/Software - C:\WINDOWS\SYSTEM32\DT\ | |
Add to favorites | "RSS" Feed | Next newer thread | Next older thread
User Post
Xkeeper
The required libraries have not been defined.
Level: NAN

Posts: -2074/-863
EXP: NAN
For next: 0

Since: 03-15-04

Since last post: 2 hours
Last activity: -753366 sec.
Posted on 04-09-05 02:54 AM Link | Quote
Once again, I bring to you this problem. There hasn't been anything 'unusual' latley (read: gallons of HD activity) and the problem ahs actually gone away... sort of. Everything chokes on this bloated DIR and I can't do anything to stop it because it's so goddamned big.

Hell, I told it to output a DIR command to a file and I'm still waiting for it to finish (it's been going for a few minutes now)

Everything's named "2004-09-28_09-42-10-63776371" -- YYYY-MM-DD_HH-MM-SS-????????"


I just opened the log it's creating... as of now there are over a hundred thosand lines in it, and it's still growing.

Deleting it isn't possible -- I've tried. It'll just hang for some reason.


Make that log over 140,000 lines now. And growing.


Anyway, if anyone could find any thing at all that could've caused this, I would greatly appreciate it -- I've only found one thing (this) and that didn't help.




Okay, it finished with 162356 lines. The directory takes up 12.5 GB of space (which is why it would likely be impossible to delete)

I'll post the DIR log soon, it's the first time I've actually been able to see it
BMF98567
BLACK HAS BUILT A SILLY DICE-MAZE!
GO!

Current list of BURNING FURY >8( recipients:
- Yiffy Kitten (x2)
- Xkeeper
Level: 53

Posts: 757/1261
EXP: 1094149
For next: 62970

Since: 03-15-04
From: Blobaria
Special Move: Rising Meatloaf Backhand Combo

Since last post: 21 hours
Last activity: 1 hour
Posted on 04-09-05 03:22 PM Link | Quote
This, maybe? I followed some links from that site you mentioned, and that's what I found. Seems odd that there isn't more info on this problem.

As tedious as it sounds, have you tried deleting the files just a few at a time? Maybe, for example, "YYYY-MM-*.*"? Maybe if you can reduce the size of the directory a bit, you'll be able to nuke it.

Also, I take it you've run ScanDisk, and it hasn't revealed any errors?
||bass
Programmer Admin
Level: 44

Posts: 298/817
EXP: 570813
For next: 40472

Since: 03-15-04
From: Salem, Connecticut

Since last post: 26 days
Last activity: 11 days
Posted on 04-09-05 03:24 PM Link | Quote
Boot into console mode and delete the files then.
Kitten Yiffer

Purple wand
Furry moderator
Vivent l'exp����¯�¿�½������©rience de signalisation d'amusement, ou bien !
Level: 135

Posts: 9223/11162
EXP: 28824106
For next: 510899

Since: 03-15-04
From: Sweden

Since last post: 3 hours
Last activity: 4 min.
Posted on 04-09-05 10:30 PM Link | Quote
I suppose your using Windows XP

Mmm, althought that could crash the computer too. Since console mode in Windows XP is basically making it start the command prompt instead of explorer.exe. That's something to try at least before doing the extremes.

If it still crashes even while doing in "Safe mode with command prompt", I would suggest trying to delete it outside of Windows. Like by using a NTFS driver for DOS (I think there was one somewhere) or by using a live Linux distro that can write to a NTFS filesystem (or by using a Linux distro on the same computer if you by any chanche have one), but doing it outside of Windows may break the whole NTFS filesystem.
Add to favorites | "RSS" Feed | Next newer thread | Next older thread
Acmlm's Board - I2 Archive - Hardware/Software - C:\WINDOWS\SYSTEM32\DT\ | |


ABII


AcmlmBoard vl.ol (11-01-05)
© 2000-2005 Acmlm, Emuz, et al



Page rendered in 0.008 seconds.