| |
ZL1UIC > AGW 10.05.04 07:40l 134 Lines 5555 Bytes #999 (0) @ WW
BID : 770594ZL1UIC
Read: GUEST
Subj: Re: Successful AGW users ?
Path: DB0FHN<DB0RGB<DB0MRW<DB0WUE<DK0WUE<F5GI<F6KMO<ON0BEL<ZL2BAU<ZL2BAU<
ZL1UX
Sent: 040510/0350Z @:ZL1UX.#20.NZL.OC #:11236 [Hamilton] FBB7.00i $:770594ZL1UI
From: ZL1UIC@ZL1UX.#20.NZL.OC
To : AGW@WW
> Hi Packeteers,
>
> Andy G0FTD wrote:-
>
>> I'd like to hear from *successful* AGW users who use the software for
>> true soundcard packet, e.g using soundcard and simple PTT interface plus
>> audio leads.
>>
>> Does anyone have it running so that it doesn't eventually crash for a LONG
>> time ?
>>
>> When I've used it with a TNC in kiss mode I never had problems, but in
>> soundcard mode it continually crashes due to it's memory leaking
>> problem.
>>
>> Is anyone successful ?
>
> The set up I have here has never crashed. It comprises of a Pentium II
> 300 Mhz running Windows XP Pro connected to an FT-8100 via a Rigblaster
> (nomic). The sound card is a Creative Sound Blaster PCI. AGW is
> version 2002.308.
System here is P 233, 64 med RAM, running Windows 98SE (this was the
upgrade edition). Running AGW 2002.0 with Baycom modem. Previously the
system ran fairly trouble-free, with the occasional "stalling; a reboot
would oseem to cure it. (I thought that was originally a Windows thing,
but now I follow on Andy's reasoning.)
It WAS fairly troblefree, until I tried to run Sally, which was a no-go,
although I did request some help to see if it would run witha baycom
modem. I got a reply to suggest using the latest version of Sally & AGW
2002.308. This still did not work, and had the added benefit of totally
killing the Winpack/AGW op[eration. I got lambasted over the missing last
3 parts of a 7+ file I was sending, because of this.
Further requests on how to re-instate the system brought a packet saying
the same thing happened to his setup doing the same thing. A reformat of
the HDD & reinstalling W95, Winpack & AGW, it still didn't work. A
different HDD was the only cure.
System runs fairly well, but the stalling still occurs, at variable
rates. Downloading more 7+ files will call a halt quickly. Basically,
itdegrades to connecting to the BBS, then stops receiving, & times out, &
disconnects. Ending Winpack & AGW & restarting will sometimes cure this
sisorder. Other times it will not connect. All incoming traffic deems to
be ignored. Alt-F4 twice & a restart will restore operation.
> I leave it running for several days at a time - it may be because I have
> 256 Mb of RAM in that PC and XP has good memory management.
Mine is on 24/7. failure can occurt anything from 36hrs to 3 days,
depending on download/uploads.
> typing this the system has been up for 15 hrs and 42 minutes and of the
> 256 Mb of RAM there is 46 Mb available, while 150 Mb is in system cache.
> CPU usage is about 10 - 15 percent.
>
> Wonder what your configuration is?
>
>
> 73 - Graham, G6YFF @ GB7WSX
===============================Pasted in===========================
From: G6YFF@GB7WSX.#32.GBR.EU
To : AGW@WW
Andy G0FTD replied to my reply, thus:
> Version 2002.308 appears to use a piece of memory for it's decoding/encoding
> purposes and once that task is done it then allocates itself another page of
> ram BUT doesn't release the last piece of ram. Accordingly you eventually
> use up all the ram and it crashes because the other ram hasn't been release
After receiving this piece of info I checked the Windows Task Manager and
found that AGWPE starts off using about 4.4Mb of RAM, then for each item
downloaded it adds about 4Kb, and indeed, seems not to release any.....
}Haven't run the system monitor/performance yet to check on what is
happening, but I suspect the same. 7+ may speed up the usage.{
My apologies for brushing your original comments about this to one side.
There again, as I seem to have suffcient RAM to last for several days at
this rate of usage (and being quite selective about which bulletins I
download), I appear to escape George's clutches in this respect. Having
got a system that works for me I am loathe to revert to an earlier version
so will stick with it until I experience such problems.
I have in my shack a spare 64Mb strip of Synch RAM @ 133 Mhz which I will
gladly subscribe to a fellow ham such as yourself at no cost if it will
alleviate your problems for a while. I can pop it in a jiffy bag and
post it tomorrow. Please let me know if you would like it.
73 - Graham, G6YFF @ GB7WSX
Message timed: 18:25 on 2004-May-09
===========================end paste============================
}with addesd comment{
Now I have my system running reasonably reliably, I will persist with the
treatment I am using, until a more successful, in-process system can be
installed to overcome the drawback.
In the meantime, Sally is a total toss-out, despite all the claims of the
protractors of the program. If it snuffs out a working system, whilst
itself remains a run-refusal record, its no bleedingood to me!
Some of the faults I experienced, I have been putting up with, (with no
explanation at the time), and of a similar vein now, with at least an
explanation, and will continue to do so. If it spits the dummy for noe
explainable reason, then it is back to DOS & TPK - at least that is a
darn good backup, as I have already experienced. Some claim DOS is a total
loss, but at times, it can still be boss!!!
So, "successful" users? With the current minor hitches, I still think so.
73 de Allen, Cambridge, N.Z. RF72RC
ZL1UIC @ ZL1UX
allengilbert@clear.net.nz
X: "Ensure brain is engaged before putting mouth into gear."
Message timed: 15:37 on 10 May 04, using WinPack-AGW V6.80, P233,
W98se, AGW-PE, Baycom modem, IC-2A, Digitor 30w amp.
Read previous mail | Read next mail
| |
