PDA

View Full Version : Paralog and N3....over it completely



quicky
Nov 7, 11, 18:10
Hi there

Well, I'm officially over it.

1. I am trying to download and use Paralog with my N3. On the help page of Paralog, it doesn't state that it works with the N3, only the N2. If this is the case, I am wasting my time completely.

2. Trying to download the USB drivers off every help link or thread leads me to an error page that says "unspecified thread...please contract administrator". I make sure I am logged in, but it still returns this error. Frustrating....and I am over trying to contact administrators.

3. When I use the minidisk to download the USB drivers, it says "cannot download as a more recent version already exists on this computer" (my PC work computer).

4. I follow a link to a help thread, that leads me to a link on another help thread, that leads me to a link on another help thread,that leads me to a link on another help thread,that leads me to a link on another help thread,that leads me to a link on another help thread,that leads me to a link on another help thread,that leads me to a link on another help thread,that leads me to a link on another help thread,that leads me to a link on another help thread,that leads me to a link on another help thread,that leads me to a link on another help thread...

5. It shouldn't be this hard. A few things come to mind here....why a mini disk in the first place? Even if the NMU were compatible with my mac, I still couldn't use the minidisk...iMac don't accept them, they are old technology. Perhaps it is simply to allow it to fit in the N3 box...not sure, but a cheap USB or complete online download would be easier. It also seems to be constantly playing catch-up, rather than being ahead of the game. I love the N3, but the software incompatibilities and incongruence is very annoying, creating a bitter-sweet after taste.

6. My NMU runs fine when I hook up my N3...yet it is still not being recognised when I follow the instructions to the device manager via the start menu etc.

All attempts lead to a dead end. And I'm over it.

My reason for wanting this is two-fold.

1. I believe in logging software. I have always used it, for all of my recreations...scuba, climbing, hiking, kayaking etc. I would love to utilise the functionality of Paralog...even if it is a little clunky.

2. I'm not sure if my global skydiving colleagues are aware of the crash that occured at my dz a couple of months ago. The aircraft stalled at low altitude, and ditched into a river bank with 5 jumpers and the pilot. Miraculously, noone was killed, but some serious accidents occured - pelvis, ribs, lungs, skulls, scalps, spines and some. Even more miraculous was that they crashed at low tide, had they ditched at high tide I am sure most, if not all, would have drowned.

http://www.cfaconnect.net.au/news/tooradin-plane-crash.html

Anyways, my close friend was borrowing my N3 to test it out as a digital alti. He had it on his wrist, and had the canopy alarms set. They intended to land with the plane due to cloud, and as they were descending (knowing there were some serious problems with their approach/the aircraft etc.), the canopy alarms started to sound for the set altitude. All of the jumpers were impressed with how the N3 delivered the alarm, and the audible warnings/lead up to the alarms. Their engagement was more of a distraction that anything else, but they were all very impressed nonetheless.

What he didn't realise was that the N3 and Paralog could map the crash profile, as the N3 thought they were under canopy, and therefore logging the jump.

So, you can understand the importance of me wanting to extract this info...apart from believing that it will be a good product to have.

I've never posted a negative thread before, but I am tired of the run around trying to trial a product that does work/doesn't/maybe/yes but not without 100 forum posts/closed circuit thread-link-thread-link call-centre type loops/computer programmer required in order for it to work (and if I must say, I'm far from an idiot).

Cheers
Jase

IanHarrop
Nov 7, 11, 18:24
Did you ever try contacting Paralog directly?

quicky
Nov 7, 11, 20:20
Hiya Ian

I have. It led me to point 4 of my thread. :(

Jase

IanHarrop
Nov 7, 11, 23:49
I didn't see in point 4 wher eyou contacted Paralog... might try this http://paralog.net/mail-form.php?Subject=Contact%20Request

Klaus
Nov 8, 11, 02:31
Hi Jase,

I searched through my email archive but could not find any relevant mails from you. Maybe you could resend them to support at paralog dot net?

http://www.http://paralog.net/prerequisites.html lists the N3 with a link to the appropriate Alti-2 forum for the installtion drivers.

Using the 'Download' link at the top of this page could be a shortcut. As you mention NMU, I assume you are on Windows. http://forum.altimaster.com/downloads.php?do=file&id=2 should take you directly to the instrcutions and downlod for the appropriate driver.

I hope this solves your problems. Please email me directly at support at paralog dot net should you need further assistance.

Klaus

quicky
Nov 8, 11, 04:13
Hi Ian, Hi Klaus

Sure thing, I'll be sure to flick through another email. Alternatively, perhaps this particular thread spells out my issues clearly?

Re: My Mac...this is what I use at home (can't wait for the NMU for Mac). As for Paralog on my Mac (Lion OS X 10.7.2 Dual Core etc. etc.)...I think I have utilised every possible link known. I have downloaded the USB drivers for my mac several times, but still hitting brick walls. I've trawled over that many threads and helpful hints in an attempt to find that vital piece of info that I've overlooked, but still not making progress. I certainly anticipated the need for double-checking N3 requirements, and have exhausted those options (at least it seems). I also try to open pages to links and downloads and it returns the error below:

403

Re: PC...this is what I have at work...I use this for NMU. I attempted to download Windows USB drivers, but it returned the message that the 'USB drivers cannot be downloaded as a more recent update is installed already'. Paralog still doesn't read my N3, even when my NMU identifies my N3 connx and opens automatically. I have tried the whole system device manager thing (a recommendation in one of the forums/links/helpful hints threads somewhere between Paralog and Alti-2), yet it doesn't show up there either.

I have tried the prerequisites pathway (your advice above)....I selected N3, yet that links up with yet another 10 forum threads. This is what I meant in my Point 4 in the initial post....the never ending loop of frustration.

Perhaps the take home point I am trying to drive home here is that the whole process has become so convoluted (and quite messy) that it is stripping the joy of discovering a new product...which saddens me. By the time I get Paralog working (and I certainly will), I'll be exhausted and over it, which is quite the shame. Would it not hurt to revise the existing threads, condense into a new, reviewed all-in-one process that stops clients from going astray before they actually discover the benefits of the products.

Surely I am not the only person here dealing with the same frustrations. Please correct me if I am wrong.

Thanks again, and kind regards
Jase