[Lowfer] ARGO Cal.

[Peter Barick]

>>> A20PJB1@wpo.cso.niu.edu 12/18/02 09:36AM >>>
> Guess that could mean the processor is overloaded.
> Hmm, it's possible some config setting can abate that
>condition ...

In answering this mail, here's what I found this morning. I believe
that ARGO_b130 on the 486 (16MB RAM)laptop would not respond because its
sampling rate of 22,050 was too high for that meager pc, as I had Mode
set to NDB, causing the ARGOs highest sampling rate, thereby swamping
the pc. Next I changed Mode to 3 sec and set the sound panel in W95 to a
lower sample rate, around 5k (was at 22k). At this point I was fishing
and the byword was "less" not "more." ARGO was started and I was able to
make changes to the app, ie, it was responding to KB and mouse
correctly.

As the above shows, I began last night trying to receive a local NDB,
"DKB," DeKalb IL., and concluded that the pc was outmoded and useless.
Now I think the 486 has some merit if run w/ proper parameters.

So New Questions:
1) What *sound card*sample parm is required for ARGO given my setup?
2) When might the sound card sample parm change and to what?
3) Other hints for a ARGO_b130-486 user?
4) Would b128 be more accommodating for the 486?

Peter