First post, by tikbalang
- Rank
- Newbie
when you see it...
you'll shit bricks.
when you see it...
you'll shit bricks.
Hmm, how did you manage to get a file named "nul"? 😳
Intel i7 5960X
Gigabye GA-X99-Gaming 5
8 GB DDR4 (2100)
8 GB GeForce GTX 1070 G1 Gaming (Gigabyte)
Maybe using Linux?
I have traveled across the universe and through the years to find Her.
Sometimes going all the way is just a start...
Use ADFstreamer to see if it's got any hidden files behind it.
Can even be done in dos, is a nice way to make a file/directory not accessible
for most people who accidentally use your computer.
wrote:Hmm, how did you manage to get a file named "nul"? 😳
Maybe it's "nul "? 😵
Probably has ALT+255 after it.
Dosfreak, I must commend you on the awesomeness of your "new to me" avatar!!! :headbang:
Dell Optiplex Gxpro: Built solely so I could re-live my SB16 days properly with newly acquired sound pieces: MT-32, SCB-55, and DB50xg 😀
tikbalang , do plz a scandisk! =DD
Everything's fine, no scandisk needed.
it was a real "nul" file, no spaces, no high-bit charcters. i could not start xp from the hd for a while and had to use the xp emergency bootdisk.
i was trying out various ntfs drivers in dos. one of them was "omnifs.exe". it didn't seem to do anything but print out its options. another was "ndos.exe" from paragon's mount everything, which worked nicely. i loaded them all in one session.
when i rebooted back to windows, i got a blank screen. the windows partition was gone. i had to recover it first before i was able to boot xp with the floppy. fixboot, fixmbr, and mbrfix all failed until i deleted the "nul" file using linux.
deleting/renaming in win explorer/console just gave a "parameter incorrect" error. i was busy shitting bricks i forgot to take a snapshot of those.
snapshots of the errors.
ESS PCI DOS Drivers
_________________