Need help setting up Etrunker - Reno

[n6brr]

I have been using Trunker and decided to try Etrunk in NV. There are no EDACS systems in my local area to test with. I could copy the NV systems great using other scanners and had strong control channel sigs, but could never get a lock on the control channel with Etrunk. I've read the instructions repeatedly and have tried using Etrunk.exe, Etrnk48.exe, esk.exe and Ed.exe with no success. Desparate, I tried copying trackenv.bat from my Trunker folder and it didn't help. I put pauses between each command line in trackenv.bat and each line errored out. I've tried normal and reverse and each different slicer pin and nothing made any diff. Obviously I'm missing some key element. If anyone is in the Reno area, are you using Etrunk or Etrnk48 for the NDOT and Washoe Co systems? I'm anxious to try this again on my next visit to EDACS country.

TIA / Gerry

 

[crayon]

Gerry,

How are you getting to your DOS enviroment? DOS Window or a boot disk?

I put pauses between each command line in trackenv.bat and each line errored out.

Something else is going on here. You should not be getting line errors from the trackenv.bat.

 

[n6brr]

I'm using Win95 and running DOS (and therefore Trunker and Etrunk) thru Windows. It has been working fine this way for Trunker. I have not tried to see what happens if I tried running trackenv.bat from the Trunker folder. It would seem that logically it should perform the same no matter which folder I ran it from. There are companion files that Trunker uses but I see no mention of any additional files for Etrunk. As there are not true instructions for Etrunk I'm not sure just what applies to Trunker also applies to Etrunk. I have never tried to examine what happens to each command in trackenv.bat when I'm using Trunker, but I suspect I am not getting the errors as Trunker works.

Thanks / Gerry

 

[crayon]

Cosmetically, there is not any difference between Trunker and eTrunker, both will use the .bat file. There are so many variables here that could be causing your problems, so I would eliminate Windows from the equation.

Since you are using Windows 95, I'm going to assume that the harddrive is formatted to FAT32. Put all of you Trunker files into a folder at the root of c:\ so that you can get to them very easily from the command prompt.

Next, if you do not have a true DOS boot disk, go to www.bootdisk.com and download the DOS 6.22 boot disk.

Getting Trunker or eTrunker to run is a very simple matter. I know this is of little consolation, but if it does not work from a true DOS boot, the only other explaination is that you might not have a real EDACS signal.

You can confirm this with T4Win ...

Good Luck.

 

[n6brr]

Crayon - Thanks for the info. I didn't try booting the PC to DOS when I was testing. I think I'm ok leaving the Etrunk files in the Etrunk directory. I'm adept at DOS and have no problem navigating in a DOS environment. I also like to keep only those files necessary on the root directory. I have some bootable DOS disks that I should be able to use after editing the config.sys and autoexec.bat files back to the bare essentials.

I think it is safe to assume I was getting a true EDACS control channel as I can monitor both the NV State EDACS system and the Washoe (Reno) County system using a BC245 and BC785 just fine. I had hoped to get some feedback from someone in the area to see if there were any quirks in those systems, but have not received any responses as of yet.

As there are no EDACS systems in my area, I'll have to wait until I hit the road again before I can make any further tests.

Thanks / Gerry