Trunker vs Military 400 mhz systems

[ColoradoRedlands]

I have recently gotten trunker up and running, and it works fine with all the local 800 and 900 Mhz systems within range.

I have a couple of military 400 mhz systems around me, and I have set the plan to "0" and have replaced the freq hex values with the real frequencies.

I don't see any radio ID's or affiliations at all in Verbose mode.

Also, do I have to put up with all the phantom input hex freq ID's appearing above the output freqs, or is there a way to eliminate them? The only thing that appears next to them are some phantom(?) ID's and unlisted type letters. (instead of G for Group, it is things like "M" or "a", etc.)

Chris

 

[SCPD]

Try the patched version by Eric Cottrell. Search this forum for links to download.

-rick

 

[EricCottrell]

Hello,

With the "stock" 3.8.3 version of trunker you need to match the input frequencies with the output frequencies for it to start working correctly. You need to edit the sys file to do this and it is described in the documentation. There seemed to be too much manual editing to get it to work.

This is one reason why I added a couple of features to trunker. It will automatically do the mapping of input and output codes. You can also create a map file for the system so it will convert the hex codes into real frequencies. I suggest you have the new trunker program create a new set of files for the trunked systems.

I do not see it in the uploads and thought it was up there. I included it in this post.

73 Eric

 

[ColoradoRedlands]

I suggest you have the new trunker program create a new set of files for the trunked systems.
73 Eric

Thanks Eric.

So that I understand you correctly, I will need to let the program create new files for only the UHF systems, or are you saying I should let it make new files for ALL systems?

Chris

 

[EricCottrell]

Hello,

Yes only the UHF and VHF. 800 MHz and 900 MHz should be fine.

73 Eric

 

[ColoradoRedlands]

Running on the beta

OK Eric,

I use an XP laptop. I am up and running with your beta. It opens in a full-screen DOS mode. Everything seems to be working pretty well, except the display is very jumpy and flickery. I do seem to be missing some radio ID's as they transmit, but it does seem to be catching about 90 percent of them OK.

Is there anything I can do to cure the jumpy display with your beta on my system?

When I run the regular M Trunker 383, it opens in a 1/4 size window under Windows and doesnt flicker, but I cant get it any larger.

I use the same short batch file (different file names) to point to the trackenv.txt, and then run the program.

 

[EricCottrell]

Hello,

I do not run Windows XP so I cannot help. I have seen threads in the Trunker group on Yahoo Groups about the problems with getting the Motorola/EDACS DOS Trunker to work with XP. I think there are some settings you have to do in addition to the batch file.

73 Eric

 

[loumaag]

Re: Running on the beta

When I run the regular M Trunker 383, it opens in a 1/4 size window under Windows and doesnt flicker, but I cant get it any larger.

Unless XP has changed Windows Key mapping this should allow you to go from full screen to window and back again. Hit <ALT>+<ENTER> to toggle. However be aware the default for DOS Windows being run the background (does not have the focus) was to suspend, so unless you change that default or leave the focus on the window (when used as a window of course) then Trunker will cease to display changes. Once again, I am not sure about XP action in this regard but all other 32bit Windows operate this way.

 

[BANDIT]

You can also edit the properties of the shortcut on your desktop. I run XP Pro and run etrunk and trunker in a window. I can change the fonts and size of the windows, or run full screen when I want to but I don't like the font of my monitor in full screen mode. The monitor is an NEC MultiSync E700. Also for some reason the beta verisions that Eric has refuse to run in a window. When the program starts I can see the window open and quickly go away to full screen. They refuse to run in a window at all. Still have not figured that one out.

 

[loumaag]

... Also for some reason the beta verisions that Eric has refuse to run in a window. When the program starts I can see the window open and quickly go away to full screen. They refuse to run in a window at all. Still have not figured that one out.

This must be an issue either with your computer or an XP issue. I have no trouble running the beta versions in a window. However, I must say that (because this is all the computer does anymore) the machine I use for Trunker is an older pentium laptop running Windows 98SE so I cannot say the beta will run as a window under all Windows OS.

 

[SCPD]

When the program starts I can see the window open and quickly go away to full screen.

Instead of point-and-click from the Windows Explorer shell, try opening a command window first and running trunker from inside the existing command window. When the program exits, the window (and any error messages) will remain.

An easy way to do so from the taskbar is ...

Start -> Run ... -> type "cmd" and press return.

When the command window appears, use "cd" to change to your working trunker directory. Type "trunker" or whatever is the name of your batchfile that you use to run trunker.

If any error messages appear, post them here. Good luck.

-rick

 

[BANDIT]

I tried that and when I quit trunker it exits straight to my desktop. No error messages or anything. I have no problem running trunker or etrunk in a window, its the beta versions that refuse to do so.

 

[loumaag]

I tried that and when I quit trunker it exits straight to my desktop. No error messages or anything. I have no problem running trunker or etrunk in a window, its the beta versions that refuse to do so.

There is nothing in Trunker, ETrunk, or the Eric's beta versions which can cause the program to close a DOS window. The action you describe is a function of the method you are opening the DOS window to begin with. If you indeed followed Rick's instructions from a couple of posts back, the window will not close to the desktop as you claim unless an EXIT command is issued.

 

[BANDIT]

Yes, I tried two ways, one by start, run, command.com and also created a shortcut on the desktop to do the same thing. When I start either of the beta programs they both close the window and go to full screen dos. When I exit with either the esc x or esc q both of them exit to a full screen dos prompt and nothing showing but the prompt, no error messages at all, then I type exit and go back to the desktop. Both beta programs are closing the window and going to full screen dos when they are started. The 3.8.3 versions do not do this using the same two methods of startup, they start up in a window. What could be the difference? Anyone else running XP and the beta versions in a window?

 

[BANDIT]

I just tried one other thing, I unchecked the close on exit in the shortcut on the desktop and tried just running trunker instead of my track.bat file. Trunker still goes to full screen dos. When I quit the program, I have an inactive trunker.exe window on my desktop with no prompt or anything, just a window that I have to close using the X or alt f4.

 

[SCPD]

Yes, they both close the window and go to full screen dos. When I exit with either the esc x or esc q both of them exit to a full screen dos prompt and nothing showing but the prompt, no error messages at all, then I type exit and go back to the desktop.

Okay, I understand a little better. The window isn't gone - it's gone full screen.

-rick

 

[loumaag]

...I unchecked the close on exit in the shortcut...

Hmm, what action did you expect to happen if you checked the "close on exit" box. You told the window to close on exit, that is what is supposed to happen. If you uncheck the box, you end up with a "closed program" DOS window (providing you are directly calling a DOS program from the shortcut program line).

If you open a DOS command window, seperate from any program, as Rick suggested then it will run just like a computer without the Windows OS. Of course that may be before you time but that is what it is supposed to do and that is the environment that Trunker runs in.

 

[BANDIT]

No not before my time. I have been using computers since the old IBM XT's and Rad Shack 1200HD. The beta programs are jumping out of the window and going full screen all on their own. If I do as Rick suggested they still do the same thing and when I quit the programs I have an empty dos inactive window on my desktop. This happens by running command.com from the command prompt or from running it from a shortcut. By the way I still have the Rad Shack 1200HD with an added turbo card in the processor slot. So darn slow I dont even turn it on any more and its just a memory sitting around.

 

[BANDIT]

By the way I have a dual boot system here with Win98 on another pertition. I just booted 98 and put the two beta's on it and under Win98 they both run in a window just fine, no problems at all, still can't figure out why they do that on XP.

 

[BANDIT]

Ok, just fired up the Dell laptop and installed the beta versions on it and same thing as with the desktop. The laptop also has Win XP and the 3.8.3 regular versions will run in a window but the beta versions refuse to on the laptop also. Is there not anyone on this forum that runs xp that can install the betas and give it a try. You dont even need a slicer, just run the programs. By the way Lou in a previous post I said UN checked the close on exit. When you create a short on the desktop, close on exit is the default. At least on my system.