Hello from Gregg C Levine (Being sent only to the new list address) Folks, here's a very strange situation. I currently have here two disk on chip devices. One is a 2 MB device, according to M-Sys, that one has been discontinued for many years, probably before I had heard about the Linux BIOS project.
The other one is a 32 MB device. That one was discontinued fairly recently. According to the folks at M-Sys, and one of their distributors, it was discontinued about the middle of 2003. Which makes sense, I bought it from a store in Manhattan who had no idea of what the thing was about the middle of last year. Both devices appear to no longer work, when I attempt to talk to them via the DOS command line tools, created by M-Sys. And only work sometimes when I used the latest release of the MTD tools from that family of devices, and drivers. And according to an HTML created documentation blob, I can't complain to the mail list about this, because since I'm using on the host machine a 2.4.29 kernel, they won't talk to me, and have switched over to the 2.6 family of kernels. My machine will boot that family of kernels, but well, the pointing device does not work. All of you are probably wondering the obvious about why I've dumped all of that into this note. Both the opening series of lines concerning the two Disk On Chip devices, (including where I bought the second), and the problems with them. This is directly connected to my actual question: Just how hard is it to render these things unreadable, or even unusable by normal methods? ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke." Obi-Wan Kenobi _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
