English French German Italian Portuguese Spanish Swedish

 

914 TCU set up problem

  • ransman
  • ransman's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
More
3 months 1 week ago - 3 months 1 week ago #22249 by ransman
914 TCU set up problem was created by ransman
I cannot get the software to load in my Windows 10. Have installed in Port 1 with the right specs. Purchase the cable that was recommended in video. Will not activate in dosbox. Any help would be appreciated.This is a new motor.
Last edit: 3 months 1 week ago by ransman.

Please Log in or Create an account to join the conversation.

More
3 months 1 week ago #22253 by Roger Lee
Replied by Roger Lee on topic 914 TCU set up problem
See if someone has a Windows 7 laptop.

Roger Lee
LSRM-A & Rotax Instructor & Rotax IRC
Tucson, AZ Ryan Airfield (KRYN)
520-574-1080 Home (TRY HOME FIRST)
520-349-7056 Cell

Please Log in or Create an account to join the conversation.

  • admin
  • admin's Avatar
  • Away
  • Administrator
  • Administrator
More
3 months 1 week ago #22266 by admin
Replied by admin on topic 914 TCU set up problem
Have you tried right-clicking the TLR icon and "run as administrator"?

Is your windows login user a member of the "Administrators" group?

Is it Win10 "Home", or Win10 "Pro"??

Are you running the 64-bit version of Win10, or the 32-bit version? ( ** there are two versions of TLR46, one for each operating system - see www.rotax-owner.com/en/support-topmenu/e...manuals#914-software )

Note: If you get the "Error 68" message, then there is nothing you can do; TLR will simply not run on your particular Win10 installation. We've had a ticket open with ROTAX engineers for more than a year on that, and to date they have found it unsolvable. Apparently some random combinations of hardware/software/drivers will kill the DOSBOX, and of course that varies from machine to machine on Windows installs... and case of "Error 68" I would echo Roger's advice, because typically we never see this problem on Windows 7!

Please Log in or Create an account to join the conversation.

More
2 months 2 weeks ago #22560 by N914MM
Replied by N914MM on topic 914 TCU set up problem
I am getting "Error 68" problem on Windows 7, 64 bit. Uninstalled and reinstalled TLR for Windows 7, 64 bit several times with same result. Also tried 2 different USB to serial cables on COM 1.

Please Log in or Create an account to join the conversation.

More
2 months 2 weeks ago - 2 months 2 weeks ago #22565 by kenryan
Replied by kenryan on topic 914 TCU set up problem
I bought the cheapest Dell laptop that Costco had - about $250 - and followed the rotax-owner instructions to the letter (including using the cable they recommend) and it worked. I couldn't make it work on my Chromebook.
Last edit: 2 months 2 weeks ago by kenryan. Reason: Add info

Please Log in or Create an account to join the conversation.

  • admin
  • admin's Avatar
  • Away
  • Administrator
  • Administrator
More
2 months 2 weeks ago #22566 by admin
Replied by admin on topic 914 TCU set up problem

N914MM wrote: I am getting "Error 68" problem on Windows 7, 64 bit. Uninstalled and reinstalled TLR for Windows 7, 64 bit several times with same result. Also tried 2 different USB to serial cables on COM 1.


Wow, we have never seen that on win7 before! Is your machine using Intel or AMD chipsets?

Also, have you applied the latest Windows updates?

Is this a new install, or has TLR worked in the past on this machine??

Please run "winver" and let me know your Windows build version ...

Please Log in or Create an account to join the conversation.

More
2 months 1 week ago #22589 by N914MM
Replied by N914MM on topic 914 TCU set up problem
Windows 7, Version 6.1 (Build 7601: Service Pack 1)
8GGB RAM, 64-bit system
Intel i7-3610QM CPU @ 2.3 GHz
All Windows updates are current
TLR has never been installed previously and has never worked
The following user(s) said Thank You: admin

Please Log in or Create an account to join the conversation.

  • admin
  • admin's Avatar
  • Away
  • Administrator
  • Administrator
More
2 months 1 week ago #22591 by admin
Replied by admin on topic 914 TCU set up problem
I suspect it could be a recent windows 7 update "breaking TLR functionality" ( It's been up and down on Win10 the last year, 'Windows Updates' frequently break more things than they fix!)

We actually do not have any machines left running Win7 here, but all of our fully-up-to-date Win10 machines are running it OK.
I would suggest that you do an image backup of the win7 system, and then try an upgrade to the latest Win10 ( might solve the TLR problem for you)

Please Log in or Create an account to join the conversation.

More
2 months 1 week ago #22596 by N914MM
Replied by N914MM on topic 914 TCU set up problem
Found the problem. The TLR46a program for 64 bit machines calls "TLR46.exe" which is not a legal command. If one types "TLR46a.exe" the program works fine. So there appears to be a small problem with the TLR46.cmd file. Please consider creating a new CMD file for TLR46a. Thanks...
The following user(s) said Thank You: admin, Gyrochook.

Please Log in or Create an account to join the conversation.

  • admin
  • admin's Avatar
  • Away
  • Administrator
  • Administrator
More
2 months 1 week ago - 2 months 1 week ago #22597 by admin
Replied by admin on topic 914 TCU set up problem
Well, I just did another clean install of TLR46a on Windows 10 (64 bit) and it works fine.

But in light of what you are seeing, it's very strange how that even works AT ALL...

Both TLR46.cmd and the dosbox-SVN_MB6.conf configuration file explicitly call "TLR46" and not "TLR46a".

But the C:\TLR\ folder only contains TLR46a.exe
And if I rename that executable to anything else (including 'TLR46.exe') then I get "Illegal command: TLR46a.exe" message from DOSBOX. (e.g. it cannot find the TLR46a.exe!)

So 'something somewhere' is actually instructing DOSBOX to run tlr46a.exe
(Maybe the installer has coded something in the registry?? ...)

I just tried editing the second-last line of TLR46.cmd to read

start "TLR46a" "%Progfolder%\DOSBox_MB6\dosbox.exe" -noconsole


AND IT WORKS FINE.

But the original cmd file written

start "TLR46" "%Progfolder%\DOSBox_MB6\dosbox.exe" -noconsole


ALSO WORKS FINE. :huh:
Here in Windows 10 64-bit, at least...


.... ah, waitaminute... :unsure:

I can edit the TLR46.cmd to call any random string, and the program still runs FINE
(example: start "ZZ" "%Progfolder%\DOSBox_MB6\dosbox.exe" -noconsole)
So, it appears that C:\TLR46\TLR46.cmd is actually not being fully parsed... the solution to your issue must lie elsewhere?
Last edit: 2 months 1 week ago by admin.

Please Log in or Create an account to join the conversation.