USB flash drives write every byte once

is it possible that these USB flash drives really have 2 TB capacity and you can only write every byte once? meaning if you erase a byte and you have a 1 GB memstick then you can erase it 2000 more times? but the old data doesn't disappear, it just gets moved away..
Action: pbug thinks about that for a bit..

otherwise I can't understand why this USB memstick all of a sudden claims to have capacity for 2 TB is someone trying to do me a favour?
Is it a typo, "T" for "G"

well it turns out they haven't because open firmware in the ibook doesn't detect htat hardware anymore no not a typo 2 TeraByte sd1 at scsibus2 targ 1 lun 0: SCSI2 0/direct removable

sd1(umass0:1:0): only the first 4,294,967,295 sectors will be used. sd1: 2097151MB, 2097151 cyl, 64 head, 32 sec, 512 bytes/sec, 4294967295 sec total or close to that anyhow.. 2097151 MB
If it's write-once, then they can use a destructive technology, like fuses.

is it possible there is a conspiracy out there and they don't want to lose erased data? they want to know what was on that stick for espionage purposes? I just don't understand why the old USB HID which was "CHEER" went away and it's SKYMEDI now and it blanked itself and I can't even manipulate the MBR with fdisk anymore.. I wonder if I can read from the raw device when I plug it in.. all 2 TB worth..
ive installed the intel compiler for linux, can i use it as an alternative to gcc?

lapert: uhm, no you'll have to rewrite all your C code now anyhow back to my USB memstick rant.. this is all this aue(4) devices fault.. when I plugged that in that's when the memstick blew up and what I don't like is that somehow they communicated.. but on the ibook both USB slots are different buses afaik so how can one bus monitor the other? and the buses were independently powered as well.. so there shouldn't have been any electricity shortages.. (I assume) anyhow I think I tried using this aue(4) device before and it was rendered useless, it wouldn't work.. maybe all this TAIWAN shit is backdoored by a common sequence to blow up each other.. fucking chinks
I doubt that's the issue.

I take that back s/chinks/capitalists the issue is that I'm suffering like millions out there who don't know how this stupid electronic shit works and it blows up for no freakin' reason, just another money drain, emotional drain as well…
could someone guide me on how to make the makefile point to the intel compiler instead of gcc

CC=/usr/local/bin/intel_cc that's all you need if intel compiler has its own assembler as well you need to modify the AS= variable
ahh and in which file would i put have to put the line?
CC=/usr/local/bin/intel_cc ?

Makefile you want to add teh real path of the intel compiler that was jsut an example
i mean where do i find the makefile?

I don't know you asked about how to make it point to the intel cc, so you must have SOME clue where it was?
no i mean is there a particular file where i have to put the line?
i know the path to the compiler

put it at the top of the Makefile if there is another line that specifies it then modify that
ahhh so that means for every makefile i would have to make the change?

no there is a global make.conf file on most systems.. you want to read the manual page on make
ahh where is that usually?

man make anyhow I'm off to bed night digital world

*
To prove that you're not a bot, enter this code
Anti-Spam Image

Leave a Comment

You must be logged in to post a comment.


Blog Tags:

Similar posts: