Basecamp crash on import export

Former Member over 13 years ago

BC3.3.1 on Windows 7 64 bit, program not responding when import / export.

I have the same and have reported it. Glad it's not just me :)

I'm hoping 3.3.2 (imminent) will resolve it

0 Former Member over 13 years ago

How much data are you importing/exporting? From/to which format?

Is it gpx? Importing/exporting large amounts of gpx data will not work, there is no fix in 3.3.2 for that. Either use gdb for large exports, or export smaller chunks of data.

We will have some improvements about this in the next feature release, but the way our gpx handling works, large amounts of gpx data will always be somewhat tricky.

0 Former Member over 13 years ago

Hi FALAGAR

the issue occurs as soon as I click on the import or export command, so I never even get as far as choosing the file type, file location etc. I've used Basecamp on Vista with no issues, I encountered this problem when setting it up on my new PC.

0 Former Member over 13 years ago

That is very odd. I run Win 7 64bit as well.

So you never get any kind of error report? It just freezes?

0 SUSSAMB over 13 years ago

Raised this earlier and explained that the error I get is a AppHangB1 error.

But initially Basecamp just feezes if you select import or export, just the same as LostGeordie is reporting.

0 SUSSAMB over 13 years ago

@ LostGeordie

Just out of interest do you have a partitioned drive? I *think* what may be happening on mine is that when I hit import/export BC polls the attached drives ... and then *sees* my partitioned 'D drive' which is some 300 Gbs, and it's that that is causing BC to 'hang'. Could be entirely wrong though :D

0 Former Member over 13 years ago

Not sure I understandd the question about partioned drive :), BC is installed on C: and I would like to use my D drive for data, is that the potential issue.?

Sorry for delay

0 SUSSAMB over 13 years ago

By 'partitioned drive' I mean do you have one physical drive that is split in two so that you have, for example, a virtual C and D drive ... sounds like you do from what you're saying, and I believe that is what might be causing both your and my PCs to 'hang'.

If BC assumes that anything other than the C drive may be the one we wish to import/export from/to then it may have problems dealing with drives over a certain size?