VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Springboard Modules (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=10)
-- Memplug Vs. Innopocket?? (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=13394)
Posted by PiDeveloper on 04-27-2001 06:56 AM:
quote:
Originally posted by pschum
faFileMver and piMover are comparable applications, although I've had piMover "crash" (?) every time I've tried to "move" (rather than copy) something from RAM to SM; faFileMover doesn't have a "move" but rather after the copy is complete the items (to be) copied remain selected and can then be deleted with the touch of another button.
If you "move" a database from RAM to SM.
It mean that it will delete that database from your visor.
If the database needed by the system. or the database is locked by its application. It may have potential crash.
It would be similar cases in other program that allow you to delete the database in the visor.
I would like to recommand to "copy" instead of "move", if you are not sure whether the database can be deleted or not.
Pls free feel to contact our support team if you still have any other problem.
- PiDeveloper
Posted by dkessler on 04-30-2001 03:33 PM:
quote:
Originally posted by pschum
And Dave: just what is the problem with some CF cards that they don't work? (Yes, I realize you're more in the software end but perhaps you can get a good answer for us!)
Well, if I really knew the answer to that question, I'd tell the hardware vendors how to fix it 
Our (Kopsis') current theory is that it's because the timing of the CS and OE signals on the Springboard bus is not fully compliant with the CF specification. The CF spec says that CS is supposed to remain valid for a certain period of time after the OE signal goes inactive and the Visor actually "drops" CS and OE at about the same time. Many CF cards don't seem to care, but I suspect that a few (most notably those using Lexar CF controller logic) can't handle the "out of spec" timing.
We're still researching this as time permits, but with most of our resources committed to software development, we don't expect a solution any time soon.__________________
<ul><li>Dave Kessler<br>President - Kopsis, Inc.</li></ul>
Posted by dkessler on 04-30-2001 03:33 PM:
quote:
Originally posted by pschum
And Dave: just what is the problem with some CF cards that they don't work? (Yes, I realize you're more in the software end but perhaps you can get a good answer for us!)
Well, if I really knew the answer to that question, I'd tell the hardware vendors how to fix it
Our (Kopsis') current theory is that it's because the timing of the CS and OE signals on the Springboard bus is not fully compliant with the CF specification. The CF spec says that CS is supposed to remain valid for a certain period of time after the OE signal goes inactive and the Visor actually "drops" CS and OE at about the same time. Many CF cards don't seem to care, but I suspect that a few (most notably those using Lexar CF controller logic) can't handle the "out of spec" timing.
We're still researching this as time permits, but with most of our resources committed to software development, we don't expect a solution any time soon.__________________
<ul><li>Dave Kessler<br>President - Kopsis, Inc.</li></ul>
Posted by dkessler on 04-30-2001 03:34 PM:
quote:
Originally posted by pschum
And Dave: just what is the problem with some CF cards that they don't work? (Yes, I realize you're more in the software end but perhaps you can get a good answer for us!)
Well, if I really knew the answer to that question, I'd tell the hardware vendors how to fix it
Our (Kopsis') current theory is that it's because the timing of the CS and OE signals on the Springboard bus is not fully compliant with the CF specification. The CF spec says that CS is supposed to remain valid for a certain period of time after the OE signal goes inactive and the Visor actually "drops" CS and OE at about the same time. Many CF cards don't seem to care, but I suspect that a few (most notably those using Lexar CF controller logic) can't handle the "out of spec" timing.
We're still researching this as time permits, but with most of our resources committed to software development, we don't expect a solution any time soon.__________________
<ul><li>Dave Kessler<br>President - Kopsis, Inc.</li></ul>
