Trunker 3.8.3 in windows 2000

[jets1961]

I know this must have been asked 1000 times but I search the forum and could not find anything.

I am running window 2000 pro and trunker 3.8.3. I can see the s level interface working fine in Slicer. Slicer sees about 1700 interrupts per second.

At one point trunker was working, but after I changed the tracevn.txt to change the slicer mode to "invert" it quite. I changed the tracevn.txt back to "normal". So everything is back like it was and now it won’t work. Is W2K just plain flakey with a slicer. I know window does COM port different in W2K but if slicer is working why not Trunker.

If anyone can point me in right direction that would be great. BTW I looked for but could not find the T4 win download anyone have the link?

Thanks, Joe

 

[loumaag]

Since slicer is working I suspect something else changed besides your modifying the enviornment file. When you open Trunker check so see if it is correctly reading your enviorment file. (Press "C" and check to see if the configuration is as you think is should be.) If the program is not coming up the way you have your environment file set, then start checking what else you changed earlier, like path, other enviornment settings on the short cut (assuming you are running this in a window).

As for T4Win, it is in the "Downloads" section off of the Home Page here, I just checked.

 

[SCPD]

You will probably notice that these applications were not designed to run as you have described it. They run in 'DOS' .. not in a Windows 'dos window'. However if you look around trunker has been ported to work in Windows .. I would try this or else wait a bit for the release of Unitrunker.

Hope this may help a little.

 

[loumaag]

You will probably notice that these applications were not designed to run as you have described it. They run in 'DOS' .. not in a Windows 'dos window'. However if you look around trunker has been ported to work in Windows .. I would try this or else wait a bit for the release of Unitrunker.

Although you are quite correct that they are DOS programs, they will run in a DOS Window quite nicely if your processor is fast enough. I will admit that running ETrunker becomes problematic in a "Window" but MTrunker runs just fine in a DOS Window providing you computer is up to it. And since, as the original poster said, it was working before, perhaps it not working now is because of one of the reason I previously stated. :roll:

 

[jets1961]

Lou wrote:

Since slicer is working I suspect something else changed besides your modifying the environment file. When you open Trunker check so see if it is correctly reading your environment file. (Press "C" and check to see if the configuration is as you think is should be.) If the program is not coming up the way you have your environment file set, then start checking what else you changed earlier, like path, other environment settings on the short cut (assuming you are running this in a window).


Thanks Lou,

I found it with the help of your suggestion. I had created a shortcut that starts in my trunker directory and runs in a full window. Then I rembered when it worked I started the program from the dos command in the start menu. I looked close at both short cuts and found this in the 'target" shortcut tabs.

C:\WINNT\system32\CMD.EXE

%SystemRoot%\system32\cmd.exe

Notice the differences, but to my surprise this did not fix it. It turns out it will only not work when I use the full screen mode. If I figure out how to get it to work in full screen mode I will let you know. Thanks for sending me on the right path.

Joe

 

[jets1961]

Start mode of trunker, normal/invert.

Now that I have trunker working, I would like to ask a question about trunker itself.

When I start trunker the "slicer mode" always starts set to "NORMAL" I always have to change it to "INVERT" manually. I have changed the line in the trackenv.txt file from:

TRACKSLICERMODE=NORMAL

to

TRACKSLICERMODE=INVERT,

but it always starts in normal. If I can't change it in software can I modify my slicer circuit to have the signal non inverted (normal) output?

Thanks Joe

 

[loumaag]

Actually using Windows (at least 32 bit) this is pretty easy. The way to do it so that you can have a "custom" setup for each system you want to track or at least each receiver you are using is as follows.

1. Set up you trunker program (TRUNKER.EXE) in whatever sub-directory you want.

2. DO NOT use the environment file anywhere on your system. If you have it in the root of your drive, get rid of it. Basically you are going to skip this part of the Trunker Set Up.

3. In the sub-directory you previously put the Trunker program, construct a "trunker.bat" file. This file should look something like this example:

@echo off
cls

SET TRACKSLICERMODE=INVERT

TRUNKER.EXE

In this batch file, set whatever enviornment variables you want, just like the example sets the mode to inverted. Make sure the last line calls the trunker program.

4. Make a new shortcut which calls the batch file you just made. Do not try and change the shortcut you made before. Shortcuts calling *.BAT files start out different in Windows 2000.

5. After you make the shortcut, right-click it and choose "Properties".
5a. On the "Options" TAB, you can choose to run it in "Full Screen" mode although I would recommend you don't.
5b. On the "Layout" TAB, make sure the screen will be 80x25 and also reduce the screen buffer to 80x25 as opposed to the default of 80x300, as you will not need the scrolling capability.

6. After this, hook up the radio, double click your new short-cut and you should be good to go.

The advantage of doing it this way, is that you can make a different batch file for each system and customize each the way you want.

 

[pro92b]

When you use the SET command, it creates an environmental variable. If you have lots of entries you can run out of environment space. Using trackenv.txt gets around that issue.

The screen should probably be 80 x 43.

 

[loumaag]

When you use the SET command, it creates an environmental variable. If you have lots of entries you can run out of environment space. Using trackenv.txt gets around that issue.

Each DOS Window launched in Windows 2000 gets a seperate memory space. You are not going to run out of space in a single setup.

The screen should probably be 80 x 43.

Opps, you are absolutly correct. Was typing too fast and not thinking as fast as my fingers were moving. :shock:

 

[jets1961]

I feel a little but I found my problem. Trunker was using it's default values as my autoexec.bat file pointing to the trackenv file did not have that special little word "set" in front of it :roll: . I guess I am getting a little rusty on my DOS commands anyway now I am

Thanks All, Joe