CPAPtalk.com

Bodhi wrote:As ResScan requires a screen resolution of 1024 x 768 to display "correctly", DreamDiver, you might want to check your screen resolution.

Or higher, I believe. Both the screens I have are higher resolution, so I suspect screen resolution is moot.

@BillBolton - I've already removed ResScan from my Win7 64-bit install, and I'd rather not re-install. I think it's a graphics card conflict. I have an ATI Radeon HD 5700 1GB. What are you using?

DreamDiver wrote:What are you using?

The current x64 desktop system I use ResScan most on has a Radeon HD 4800 1GB in it, but the x64 laptops I have also used it on when travelling have several different Intel and ATI GPUs in them.

Cheers,

Bill

billbolton wrote:

DreamDiver wrote:What are you using?

The current x64 desktop system I use ResScan most on has a Radeon HD 4800 1GB in it, but the x64 laptops I have also used it on when travelling have several different Intel and ATI GPUs in them.

Cheers,

@Bill

Bill,
I decided to reinstall 3.13 to see if the results would be better. They are similar.
I've made this short video to show the problem.

DD, you may simply be victim of a new video card/GPU that simply doesn't handle very well the graphics code in the old library files that ResScan is built with. Take a look in the ResScan3 folder and you'll find a number of DLL/BPL files from Borland that are over 10 years old. There are even older Microsoft foundation class libraries being used. I've got a Mobile Intel GMA 4500MHD 1Gb that is horribly slow when ResScan first draws the graphs, though I can drag and drop reasonably well.

I hope you find a solution and prove my guess wrong!

TooGroggy wrote:.... What was Resmed thinking putting the data there?

The location of the patient folder is overridden under Win7. Win7 enforces a rule that disallows data files from being placed in a common area, such as the Program Files folder. Microsoft has recommended for years that all data files go in the "My Documents" (or whatever it's called in Win7), but didn't enforced it in earlier OSs. So, while it's Win7 that is relocating the files, it is doing so because Resmed failed to follow Microsoft's coding recommendations. And the reason Win7 is doing that is so that other (non-admin) users of the computer can't see the data.

BernieRay wrote:DD, you may simply be victim of a new video card/GPU that simply doesn't handle very well the graphics code in the old library files that ResScan is built with. Take a look in the ResScan3 folder and you'll find a number of DLL/BPL files from Borland that are over 10 years old. There are even older Microsoft foundation class libraries being used. I've got a Mobile Intel GMA 4500MHD 1Gb that is horribly slow when ResScan first draws the graphs, though I can drag and drop reasonably well.

I hope you find a solution and prove my guess wrong!

It's entirely possible, but consider:

• I'm using a Sandybridge i5 2500K 8GB RAM with an XFX ATI HD Radeon 5770 1GB 128-bit card that has been available since 2008 - before Win7 and 64-bit were popular. It's a very good card at a very low price-point. Because it's that 'older model', it ends up being very useful should I decide to make my machine into a dual boot with hackintosh.
• When running WinXP Mode (virtual pc under windows 7), the graphics are flawless. (It actually runs better and faster than the Dothan Pentium M laptop with an ATI Mobility Radeon 9700 256MB card I have had since 2004. This little laptop was considered a fairly slick laptop six years ago.) Hence, I doubt the graphics card is at fault. More likely, as you suggest, the dynamic linked libraries, etc., are ancient. ResMed may need to recompile some of them for 64-bit. That takes time and money, and I'm guessing they'll wait until there is a large enough community of 64-bit users to warrant it.

I doubt many DME corporations move quickly with regards to upgrading machines. I don't doubt there are still people using Win2K. From my perspective, Microsoft only ditched Win2K because it was so stable nobody ever called the techs to fix anything. I never got blue screens on that OS. In fact, I still have a virtual machine I made from the OS I imaged off an old machine I donated to a local non-profit. (They erased the HD and put Ubuntu on it.) I still boot up my little Win2K VM for stuff that won't run on anything newer.

Time and money. Dirty words. How about we start saying 'sails and wind' instead?

I agree - if it's fast in XP mode, it's almost certainly a ResScan libary/Win7 issue and it very well could be made worse by the 32 to 64 bit conversion. Which stinks...

Sails and wind does put a nice spin to a worn phrase!

DreamDiver wrote:I've made this short video to show the problem.

I'm on a Lenovo T400, using a Mobility Radeon HD 3400 GPU, under Windows 7 Ultimate x64 right now.

After watching your video I tried the same operations. The moving around of the order of displayed graphs is slow (but AFAICR, its not paticularly better/worse than its always been for me). The screen resizing from partial to full screen doesn't show the rendering problem you are having.

Cheers,

Bill