I'm surprised it's missing another point of fast cards: power saving.
Even though different cards use different amounts of power for read/write operations they're all in the same ballpark because they need to respect the SD specification. As with all flash memory it usually consumes far more power when reading and writing than idling (particularly erasing/writing).
So if the camera spends more time flushing the buffer because the card is slower, guess what? The camera is spending more juice in an unusable state.
I consider the memory card price to be part of the overall camera package, like the carrying case.
For me going with the cheap option is a bad idea, specially when you start looking at the pictures and have a couple of corrupted shots.
Like a cheap carrying case that starts breaking down after some time of use.
That would be double standards.
For instance, it seems ok to many people that Check Point Software was founded by an ex Unit 8200 member, right?
Seems like it's a "they're not our kind of friends" thing and political leverage heading into elections soon.
Deja Vu!
Just yesterday i repaired mine with a power supply problem.
And quite a nasty problem.
The metal brick the scanjet has underneath contains the main electronics PCB which has all the logic and also a second-stage power supply that generates all the regulated voltages like +5V, +12V and so on.
My brick also has +37V without load, but that's normal - it's just a transformer with a rectifier with no regulation.
With the scanjet connected it's around +34V, but anyway everything is regulated so no problem with that unless it goes too high.
Anyway, the problem itself was with the PCB in the scanner, not the brick. My symptom was that the scanner sometimes turned on, sometimes it didn't, specially when moving it around.
The fault: material fatigue. The trace going from the negative input from the connector got almost cut at some point.
The order in the PCB is something like: negative input -> L1 (or L2, don't recall exactly) -> ferrite filter bridge -> capacitor.
The cut was between the ferrite bridge and the capacitor or somewhat between that.
The fix: a simple soldered cable from the negative input on the PCB to another big ground on another part. Of course this probably renders your scanner to be non-FCC compliant or such, but anyway FCC doesn't matter here in Argentina;-)
Works... but i wonder how long it'll last until another trace is cut...
For all the crapware i use vmware.
Sure, you've got to pay for it, but then it'll save you lots of headaches dealing with this stuff.
Just use a virtual machine for the crap, and the main one for the real stuff.
Probably bochs would also do, though i didn't test it.
It actually runs linux, check on Montavista's site... they have the Linux LSP available for download for Alchemy's (sorry... AMD) au1000 which is the ancestor (just no lcd/sd controller, a little more power hungry) of the au1100.
But you'd rather use Alchemy's au1500 which has a pci bus controller i guess...
Slashdot Mirror
I'm surprised it's missing another point of fast cards: power saving. Even though different cards use different amounts of power for read/write operations they're all in the same ballpark because they need to respect the SD specification. As with all flash memory it usually consumes far more power when reading and writing than idling (particularly erasing/writing). So if the camera spends more time flushing the buffer because the card is slower, guess what? The camera is spending more juice in an unusable state. I consider the memory card price to be part of the overall camera package, like the carrying case. For me going with the cheap option is a bad idea, specially when you start looking at the pictures and have a couple of corrupted shots. Like a cheap carrying case that starts breaking down after some time of use.
That would be double standards. For instance, it seems ok to many people that Check Point Software was founded by an ex Unit 8200 member, right? Seems like it's a "they're not our kind of friends" thing and political leverage heading into elections soon.
Deja Vu! ;-)
Just yesterday i repaired mine with a power supply problem. And quite a nasty problem. The metal brick the scanjet has underneath contains the main electronics PCB which has all the logic and also a second-stage power supply that generates all the regulated voltages like +5V, +12V and so on.
My brick also has +37V without load, but that's normal - it's just a transformer with a rectifier with no regulation. With the scanjet connected it's around +34V, but anyway everything is regulated so no problem with that unless it goes too high.
Anyway, the problem itself was with the PCB in the scanner, not the brick. My symptom was that the scanner sometimes turned on, sometimes it didn't, specially when moving it around. The fault: material fatigue. The trace going from the negative input from the connector got almost cut at some point. The order in the PCB is something like: negative input -> L1 (or L2, don't recall exactly) -> ferrite filter bridge -> capacitor. The cut was between the ferrite bridge and the capacitor or somewhat between that.
The fix: a simple soldered cable from the negative input on the PCB to another big ground on another part. Of course this probably renders your scanner to be non-FCC compliant or such, but anyway FCC doesn't matter here in Argentina
Works... but i wonder how long it'll last until another trace is cut...
For all the crapware i use vmware. Sure, you've got to pay for it, but then it'll save you lots of headaches dealing with this stuff. Just use a virtual machine for the crap, and the main one for the real stuff. Probably bochs would also do, though i didn't test it.
It actually runs linux, check on Montavista's site... they have the Linux LSP available for download for Alchemy's (sorry... AMD) au1000 which is the ancestor (just no lcd/sd controller, a little more power hungry) of the au1100. But you'd rather use Alchemy's au1500 which has a pci bus controller i guess...