Author Topic: "cannot copy dmenu\: the file or directory is corrupted and undreadable"  (Read 2421 times)

Dave B.

  • Guest
It all started after downloading the new 0.34 beta local pack. When installing this local pack, when it got to the dmenu directory, specifically the .screen file, it would give the message "cannot copy dmenu:\ the file or directory is corrupted and unreadable." I tried redownloading the local pack but it gave the same message when getting to .screen in dmenu. I then proceeded to reinstall 0.33 all over again starting with 0.33a and to my surprise, I get the same error again! I have no idea what could be the issue here as I've re-downloaded 0.34 beta and still got the same error as if it were a incomplete/corrupt download. 0.33a-0.33c installed just fine the first time, but now I seem to be getting this error message everytime it gets to the .screen file in the dmenu folder (or just the dmenu folder itself) when installing it. :'(

QBert

  • Guest
Re: "cannot copy dmenu\: the file or directory is corrupted and undreadable"
« Reply #1 on: January 06, 2010, 08:28:56 pm »
It happens occasionally. Here's what to do.

First, back up any saved games you want to keep. Then, fully format your SD card (32KB cluster size). Copy zImage, then rootfs, then the /local/ directory. Copy back your saved games (unless you already put them in the /local/ directory) and you should be good to go.

Chris23235

  • Posts: 603
Re: "cannot copy dmenu\: the file or directory is corrupted and undreadable"
« Reply #2 on: January 07, 2010, 10:48:55 am »
Now, it would be the best to fomat your card, as QBert suggested, but if a corruption appears later again (possible in Dingux, even on a 32 KB cluster size formatted card), you don't have to back everything up, format you card and copy everything back, cause that is to time consuming.
Just use the Windows chkdsk program. You have to access it from the command promp, then type

chkdsk [letter of the drive your Dingux SD card is inserted] /F /R /X

This fixed all corruptions I ever saw on Dingux. In general, you can't avoid corruptions on Dingux 100%, but if you use 32KB Cluster size and shut the Dingux down with Reboot or PowerOff, you can make them more unlikely. Just don't use the reset switch, while in Dingux.

 

Post a new topic