Tiny Core Base > Release Candidate Testing
tinycore_2.4rc1
bmarkus:
--- Quote from: Jason W on September 21, 2009, 10:47:50 AM ---Those files are getting an I/O error when trying to read them with any app. They are apparently corrupt files and I will replace them.
--- End quote ---
Hm... In my case how is it possible that I can verify them and they are getting installed and working?
Will try it with other machines. What is strange that never seen this before 2-4rc1 I know, anything can become faulty any time ;D
Jason W:
The use of copy-to-ram exposes corrupt files and other errors that are not caught by mounting a tcz or untarring a tce. Rox filer for some reason was a similar case for unknown reasons. The wxgtk extension has been fixed and reposted.
bigpcman:
--- Quote from: Jason W on September 21, 2009, 11:01:23 AM ---The use of copy-to-ram exposes corrupt files and other errors that are not caught by mounting a tcz or untarring a tce. Rox filer for some reason was a similar case for unknown reasons. The wxgtk extension has been fixed and reposted.
--- End quote ---
This is a very interesting limitation. I wonder if there is a remedy.
Jason W:
Not really a limitation as there should be no corrupt files in an extension anyway. Copy to ram simply exposes them. The remedy is to have no corrupt files in extensions. I will post a new extension audit script that will check for corrupted files so they can be caught before submission.
bigpcman:
--- Quote from: Jason W on September 21, 2009, 12:41:20 PM ---Not really a limitation as there should be no corrupt files in an extension anyway. Copy to ram simply exposes them. The remedy is to have no corrupt files in extensions. I will post a new extension audit script that will check for corrupted files so they can be caught before submission.
--- End quote ---
--- Quote from: Jason W on September 21, 2009, 12:41:20 PM ---Not really a limitation as there should be no corrupt files in an extension anyway. Copy to ram simply exposes them. The remedy is to have no corrupt files in extensions. I will post a new extension audit script that will check for corrupted files so they can be caught before submission.
--- End quote ---
I suppose the more likely problem is going to be that the extensions become corrupt in the /tce directory. Perhaps the extension audit menu tool could also check the "health" of the extensions.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version