T4WIN/EDACS

[Jay911]

I've been running T4Win 24/7 on a local Motorola system for a few weeks now and decided to move to other systems to gather info on them... first one I tried was my local EDACS system, which I've had good success with before.

These days, it seems to work okay for a while, then craps out while I have my back turned (maybe the computer doesn't like me or something ). T4Win "encountered and error and will now shut down", i.e. the typical Windows crash message. This happens irrespective of the computer I'm using - I have T4Win installed on two 98SE machines and two XP machines (one Home, one Pro, both SP2) and it exhibits the same behavior across the board.

Anyone else having trouble with EDACS? Could it be that I'm occasionally getting a dropped signal strength and the program is not liking that?

Anyone care to try a recorded sample taken when a crash occurs?

Rick, would a cut and paste of the register values (etc) from the crash dialog do any good for you?

 

[Chris-M]

Yup

I'm having the same problem. No clue as to why it's doing it. Running Windows XP Pro on a Toshiba 850mhz laptop with 256MB ram.
I'll run it in a few minutes and note how long it was running before it crashed and note the register values also.

 

[DaveNF2G]

When a program runs for a while and then crashes, I'd suspect a memory problem. It's either defective computer chips or, more likely, what some call a "memory leak" where a program uses progressively more memory as it runs and eventually tries to use more memory than the system allocated for it at startup - or invades memory not assigned to it.

 

[SCPD]

Rick, would a cut and paste of the register values (etc) from the crash dialog do any good for you?

No ... the code has changed ... it's likely the register values wouldn't match the map files I have here. I'd have to create a new "checked" build, have you run that for a while, and compare any crash results to the map file.

-rick

 

[Pro-95]

Rick,

Are you still working on T4Win or is the 96dump getting all your focus?????

 

[Pro-95]

Rick,

If you want to create another "checked" build I'll be more than happy to run it for you as well. As it seems I haven't paid my dues or prayers to the Windows gods lately and T4Win is suffering from crashes here also. I'm even having difficulty with opening an existing file and T4Win creates another seperate EDACS96 database.

ACK.

 

[loumaag]

... Also Rick,

When you are ready to implement real VHF/UHF ability and Type I fleetmapping, I have all of them here to test on.

 

[scanfan03]

I can test 400MHz LTR, 800MHz EDACs, and a 900MHz Type II system here.

 

[SCPD]

Sorry guys ... I'm not ignoring you ... just busy with some P25 related stuff. *sigh*

-rick

 

[ronneal]

Hey guys

You are not running enough system memory in your systems and video card memory. Annd I would recomend that you switch to Windows 2000 Pro
It is a more stable platform to run. Its not a memory HOG like XP.

The more memory you have for system the better it will work. And 256 mrg video card only cost $ 88 at newegg.com Look at the Apollo brand its Mivida chipset and has a cooling fan on board

 

[SCPD]

You are not running enough system memory in your systems and video card memory. Annd I would recomend that you switch to Windows 2000 Pro It is a more stable platform to run. Its not a memory HOG like XP.

XP may be a memory hog but T4Win is designed to conserve CPU and memory resources (you can see this in task manager). It's not graphic intensive like Quake or Doom so upgrading video won't help.

The issues reported in this thread are bugs in actual code ... changing configuration won't make them go away. This program is being rewritten so address a number of issues - like UHF decoding, odd crashes, and so on.

-rick