Difference between "T4Win" and "MTrunker port

[astrodanco]

Okay, I hope this isn't a completely idiotic question. If so, then I can take my lumps, so feel free to dish 'em out. :shock:

What are the main (functional) differences between "T4Win" and the new "MTrunker ported to Windows?"

 

[r00t]

MTrunker32 is using dos compatible database files - T4WIN is using XML data. MTrunker32 looks like old DOS prog and have same hotkeys.
In both programs are wide scaner support and soundcard decoding is also very good (I am using FIR filters, don't know anything about T4WIN). I want to port EDACS versions too, so this system will be decodable in next version.
MTrunker32 will have one special feature: one scanner mode - it will filter audio (no anoying control channel) and automatically jump to channels where is something interesting (using priority system). I think that this will be very useful for people who have only one scanner (when travelling, or for beginners, etc.).

So now it's much more about interface. T4WIN is windows gui application controlled by mouse clicks (not 100% true), MTrunker32 is console based, using keyboard shortcuts. If you know how to use old DOS trunker, you also know how to use MTrunker32.

Maybe this sounds like I am only promoting my new application... 8)
but I ported MTrunker because I don't like T4WIN interface, so this post is showing my opinion to it.

r00t
http://www.r00t.cz/

 

[SCPD]

There has been a demand for a Windows compatible version of Trunker and ETrunk for some time. Quite a few folks that lug around an old 486 laptop just so they can run trunker. (You know, the 15 pound brick with scratched screen, three missing keycaps, and a battery that lasts just 90 seconds without the AC adapter). This new version will allow them to use more current (and convenient) hardware.

[ r00t - if you'd like to add slicer input capability - I can send you the source code to Trunker-XP. It might also fix Type I vs. Type II issues. This code does not include Eric's VHF/UHF update. ]

A few more differences ...

1. The source code for T4Win - like the original DOS trunker - is publicly available.

2. T4Win supports multiple protocols: Motorola, EDACS, and - very soon - P25.

3. T4Win supports data slicer and sound input.

4. T4Win supports multiple receivers for signal input (monitor two or more systems at once).

5. T4Win supports multiple receivers for computer control (listen to one or more voice conversations).

The user interface for T4Win is about to undergo a dramatic change. But before that happens, I need to release a P25 version of Trunker.

Regards,
Rick

 

[pro92b]

This new version will allow them to use more current (and convenient) hardware.

I can use my P4 2 GHz Thinkpad with DOS Trunker by booting from either a floppy or USB pen drive. Works fine.

T4Win supports multiple protocols: Motorola, EDACS, and - very soon - P25.

So where's the LTR, Multinet, Passport, MPT1327, ESAS, Tetra, and Nextel decoding? :lol:

The user interface for T4Win is about to undergo a dramatic change. But before that happens, I need to release a P25 version of Trunker.

Christmas gift? :lol:

 

[SCPD]

Christmas gift?

Hi Bill!

Yeah, the P25 decoder - to go along with the P25 trunking packet disassembler (that's a mouthful to say out loud) were supposed to have been released last week. A very crude Trunker-like program will be ready in a few days.

Of course, if you have a PRO-96 - you'll want to use pro96com.

As for iDEN, send me the specs on the data link layer, and I'll write the 16QAM demod software to run it.

ESAS? lol

-rick