Dump dll from wm2003 to fix cf gps problem

Corvin · 03-15-06, 01:29 PM

Seems I've posted in wrong forum, moving here...

Hello.

Me, like many others here, unfortunately have a problem with my cf gps card...
It's holux gm-270 ultra CF card and the problem is the same famous one. While Dell seems to know about the problem and promises fixes, I'd want to try something elese in the meanwhile. The idea is inspired by elserial.dll hack posted by Beamer, it helps but not completely, software loses and finds the card all the time... So I thinked why not to try and use serial.dll from wm2003, from x50v rom image (I have x51v but AFAIK they share mostly the same hardware...)

So, my question is how this can be achieved, how I can dump dll from wm2003 image, what are the needed tools and where do I get the image from? If someone has all the needed tools and will be so kind to send me the serial.dll itself, I'd be very thankful also

Thanks,
Alex.

Rob Barron · 03-15-06, 02:30 PM

As far as I can see, the main problem that is causing all these CF probs on the X51v is that whilst it has a CF slot, it is specifically a CF II slot so anything that is CF I might not work. The problem is with most CF products, be they memory cards, GPS receivers, WiFi, etc is that they usually just list as being CF without stating whether they are I or II.

My CF GPS receiver definitely doesn't want to know despite it working absolutely fine on my Axim X5 with Tom Tom 3. I have TT5 on my new X51v but have so far failed to use it as I can't even get the new BT GPS receiver I bought to work with it. To say i am getting frsutrated is an understatement. I am no techie so when it says 'What Com port do you want to use?' how on earth am I supposed to know that or find it out?

I am convinced that PDAs are brilliant for anyone who wants diary functionality but for deeper use, web browsing etc you need a degree in modern technology! I mean, should a standard user really have any reason to know about .dll files, hacking registers and all this stuff? Surely this stuff should work from the tin so to speak. I bought my Axim X51v because it is marketed as being the best, it says it browses the internet, can check my emails, all that stuff. But the book is worse than useless in telling me exactly how to set it up to use with my ISP (I am on AOL but will happily join another ISP to get it working if necessary).

Anyone fancy stopping this 44 year old bloke from going prematurely bald?
Cheers,
Rob

JakeRich · 03-15-06, 02:58 PM

Rob, I don't think there is any difference between TYpe 1 and Type 2 interfaces. The difference is the thickness of the card and the slot for it. Type 2 are thicker cards, typically for micro-drives, etc. Type 1 are thinner, for memory, etc. The interface is, I believe, identical no matter the type.

03-15-06, 03:14 PM

What programs do you use?
elserial.dll have solved all my problems but with TTN5. For TomTom Navigator I've developed a small ptogram that solve the issue.

Corvin · 03-16-06, 01:39 AM

I'm using navngo-Israel and destinator...

Navngo failed to see the card completely, now it does see it but loses it every 2 seconds or so and never passes an early stage of looking for sattelites.
Destinator did see the card but lost it quite frequently, stopped receiving signal and did a lot of routing mistakes as a result, this seems to improve with new dll but not solved completely...
However, I believe that an old serial.dll will solve all these issues, if only I knew how and where to get it :(