Tim
Excellent tip.
Downloaded the latest ATI drivers for my FireGL X1-128, uninstalled the old
drivers (ugh forgot what a crummy display BASIC windows video drivers produce),
cold boot W2k FOUND new video device, hit cancel, ran ATI setup !voila!
display is good in P8 with DirectX now.
There
First off, I want to join the others
in complimenting Eric and crew for a really great release. The following
are my observations so far.
Hardware/software used:
AMD Athlon 2X 64 4400+ (~2.2 Ghz)
with 1 GB RAM
NVIDIA GeForce 6200 graphics
controller
Delta 44
.NET 2.0 and DirectX
I attach my worst case difference screen captures. One is blackham
harris operating on a pure tone. The other is polyphase operating on
exactly the same tone. I presume you can see the difference here.
Certainly can - most impressive.
To demonstrate this for myself I used an Elecraft XG1 on
Hi Eric,
I am sorry to have missed the teamspeak forum and the Xylo forum this
week, having been preoccupied with wrapping up some other projects
before I start the new job on Monday. After things settle down in a
week or so I will get back to the SDR fun. Overall, this move should
allow me
Hi Cecil,
The microscope has an 8 working distance. The 10X magnification
seems about right.
73 de Phil
On 12/18/05, KD5NWA [EMAIL PROTECTED] wrote:
Wow, I like that microscope, vision problems is a big issue with me, I find
it very difficult to work with all this SMT stuff. But if you
Indeed. The thing people will probably notice most quickly in our
narrow bandwidth zoomed windows (given the horrid key clicks on most CW
transmitters) is that the detail in the noise floor and in the speech
formants, etc. become sharper and more detailed. It is a win and the
increased
Phil,
This is something that I will be trying on Monday and it is a good idea. I
had hoped to automate that process, but it looks like it will just have to
be a selection. It is strange that you would get different behavior just
because the first attempt to create the DirectX device with
Hi Eric,
On 12/18/05, FlexRadio - Eric [EMAIL PROTECTED] wrote:
Phil,
This is something that I will be trying on Monday and it is a good idea. I
had hoped to automate that process, but it looks like it will just have to
be a selection. It is strange that you would get different behavior
Tim Ellison wrote:
OK, here is the skinny. After reading all the posts today on the Fatal
Error Syndrome, it kept occurring to me that something in the video
driver / DirectX arena was probably the culprit, so I focused my energy
there. I ran DXDIAG, an it said everything was fine and dandy,
Bob/Eric,
I did a bit of comparison between different versions I had installed
and found
that on my hardware, preview 8 runs with about the same CPU consumption
as preview 1. Preview 7 was a significant cpu hog on my config for some
reason.
fft_wisdom was run on all versions and I imported
John,
The only way I get my CPU utilization down is to cause an Unhandled
Exception. Once that happens, CPU utilization is about 3%
-Tim
---
Tim Ellison ( [EMAIL PROTECTED] )
Integrated Technical Services ( http://www.itsco.com )
-Original Message-
From: w2agn [mailto:[EMAIL
Well I downloaded 8 today and my cpu is at 30-45%...But works good..Bob
I just tried downloading version 8 to 4 different computers.
Gateway P4 2.4 GHz 1 M Mem Windows 2000--Loaded fine
Gateway P4 1.8 GHz 512 mem XP--Loaded fine
Compaq Presario 2100 Lap Tp AMD 2.1 GHz XP Home could not complete program
loading
Home built P4 1.8 GHz 512 Mem XP-could not complete
I found the web site that will tell you more than you really want to
know about how to install and tweak graphics adapters based on NVIDIA
chip sets with DirectX and OpenGL.
http://www.tweakguides.com/NVFORCE_1.html
-Tim
---
Tim Ellison mailto:[EMAIL PROTECTED]
Integrated Technical Services
Eric,
Here is an observation or two and not a necessarily a commentary on
higher CPU utilization with DirectX
In DirectX mode, I get a bunch of Unhandled Exception errors when using
the GUI (clicking on buttons and such). If I click on the button to
continue, CPU utilization goes from 25% to 3%
At 11:16 AM 12/18/2005, Tim Ellison wrote:
Eric,
Here is an observation or two and not a necessarily a commentary on
higher CPU utilization with DirectX
In DirectX mode, I get a bunch of Unhandled Exception errors when using
the GUI (clicking on buttons and such). If I click on the button to
Well gang, seeing that I was using preview 8 with my softrock, still
thinking about another sdr1000...
Sony Vaio Desktop
Pentium 4 3.0 GHz
504 MB Ram
Windows XP home, now Pro
Firebox
45 - 50% CPU
Was really happy with the result until I tried DirectX, then I restarted to
a blank screen. No
Its a stock RB-40
Wow. There is no way that I know of that would cause PowerSDR to
automatically go from DirectX to GDI+ as you described. More likely,
whatever is hanging up the DirectX stuff crashes upon subsequent calls and
then it quits doing whatever it was doing before, thus freeing up the
cycles. After
OK. I can believe that once the DirectX stuff crashes, then it quits
what it is doing. The display continues to work (for a little while),
but it is very unstable. Eventually the exceptions will actually crash
the entire application and that is when I get video (something?)
corruption that so
More preview 8 observations:
I am running an Asus Pentium 4 cpu, 3.2 Ghz, and 1 Gbyte ram, Radeon
9600 series video, Delta 44 sound card. In the SDR setup screens,
Display tab, Direct X was chosen for the Driver Engine and Polyphase
FFT is enabled. When preview 8 is first initialized cpu
21 matches
Mail list logo
