"Jetmouse keygen is a brilliant tool, just a bit tricky to understand for some folks.
1. Launch the keygen, and type in your 10# (10 digit decimal) SD-Card ID into the "Unit ID" field.
"
Jedtmouse keygen is very easy to understand and use but....
unfortunately again my question has been completely misunderstood!
You say to type in the 10 digit SD_Card ID....
but the SD_Card ID discovered by the software and by Microsoft Checkdisk program is 8 digits, not 10.
That is why I asked if it is a hex code that one can convert into the 10 digit code needed by programs such as Jetmouse Keygen
Also, many hex codes are displayed reversed so that the first five numbers un-hexed into decimal are actually the last five in the 10 digit numbers.
It seems that no-one on this forum can answer that question.
Example of SD_Card id:
e.g. micro sdCard
Partitiion ID: 3461-6432 (8-digit number in Hex?)
3461(Hex) = 13409 (Decimal)
6432(Hex) = 25650 (Decimal)
So the ID number to plug into Jetmouse is either 1340925650 or 2565013409.
It seems to be very hard to stop the spreading of the "urban myth" that a disk volume serial number is the same as a memory cards CID (128 bit Card identification number: individual card number for identification). I've tried many times to explain that it doesn't work that way.
The CID is permanent in the memory cards internal register. The volume serial number changes when the volume is reformatted.
There's also tools to change the Volume ID (volume serial number). If that worked to change the CID then everyone could easily clone a Garmin map from one memory card to another. No such luck with the volume method though.
While WinNT/2K and Windows 9x's built-in Label utility lets you change the labels of disk volumes, it does not provide any means for changing volume ids. This utiltity, VolumeID, allows you to change the ids of FAT and NTFS disks (floppies or hard drives).
Usage: volumeid <driveletter:> xxxx-xxxx
This is a command-line program that you must run from a command-prompt window.
Note that changes on NTFS volumes won't be visible until the next reboot. In addition, you should shut down any applications you have running before changing a volume id. NT may become confused and think that the media (disk) has changed after a FAT volume id has changed and pop up messages indicating that you should reinsert the original disk (!). It may then fail the disk requests of applications using those drives.
If you have a Windows Mobile, Windows PPC or Windows CE unit you can try this tool.
Attached Card_ID.rar that reads correct CID by using Windows CE / PPC / WM: [Only registered and activated users can see links. ]
Bookmarks