N Gauge Forum

Notices, Help With Problems and Your Forum Ideas... => Computer Help => Topic started by: Geoff on March 02, 2014, 08:24:37 AM

Title: Digitrax PR3
Post by: Geoff on March 02, 2014, 08:24:37 AM
I am having a real issue with my PR3 drivers and my windows 8 Laptop, I have loaded the drivers following to Digitrax instructions but I do not get a green light with Railroad and Co's software, and Decoder Pro just crashes, has anyone else had this problem with the PR3 and did you get round it at all.

I am in need of major help with this one.

Any advice would be fantastic.

Many thanks in advance.

Geoff
Title: Re: Digitrax PR3
Post by: EtchedPixels on March 02, 2014, 10:19:12 AM
There is a digitrax yahoo group plus a digitraxsound one. I have vague recollection of seeing a workaround discussed there. There also seems to have been a set of software updates when the newer decoders came out
Title: Re: Digitrax PR3
Post by: Geoff on March 02, 2014, 11:12:19 AM
I have posted on the Digitrax yahoo group and no takers yet, surely this is a common problem.
Title: Re: Digitrax PR3
Post by: EtchedPixels on March 02, 2014, 11:30:45 AM
Its mostly been windows 7 problems.. the drivers they were shipping and maybe still are only went up to 32bit XP.

I don't unfortunately know the details as I don't run Windows. In Linux we made sure the base OS knows both the Digitrax programmer and the Sprog. I'm pretty sure we added the Hornby units to the kernel too 8-)
Title: Re: Digitrax PR3
Post by: Geoff on March 02, 2014, 03:43:01 PM
OH dear I have just installed the latest Firmware for the PR3 and it is all up on running on my works Laptop, well that is a step in the right direction, The sprog is working fine with the PR3 just need to try Railroad and Co software.

Many thanks for your input Alan.
Title: Re: Digitrax PR3
Post by: Caz on March 02, 2014, 06:19:32 PM
Sometimes selecting MS100 mode instead of PR3 gets it working.
Title: Re: Digitrax PR3
Post by: Geoff on March 02, 2014, 06:29:02 PM
I have found out that the PR3 does not like USB 3 so that is why it was not initially working so maybe that is where the problem seems to be.