Windows 7 Installs

Rather than adding a new thread each time I come across a strange quirk in W7 installs of Opus, I thought it might be more helpful and less messy if I post one thread, and others might be able to add or help in one place. I hope that's OK.

The quirk that prompted this post is one that I have been able to duplicate, and was one which I was watching for this time.

After answering NO to all the integration questions during the install (leave FTP handling alone, leave ZIP handling alone, leave default image/sound/video handling alone), Opus has defaulted to handling ZIP files. This is something I definitely HAVE had major headaches with over the past 18 months, so I wanted to post this minor issue here.

When I finished installing, which didn't require a reboot, despite asking Opus to start with windows, when I opened up the ZIP preferences page, the "Activate Opus ZIP file handling" is set to true, even though the next setting (use Opus as the default ZIP handler) is set to false.

My issue with this is that I manage my zip files better than Opus does (no offence intended), and it's actually pretty annoying when I double-click a zip file so I can open it and deal with the contents myself, and instead Opus opens it in the current lister. I'm not sure if that's what's intended, but that's what happens.

It's an easy fix, but it would be nice to not have to do that after an install.

The prefs dialog also seems to have problems painting the folders pane of the prefs (the left-most pane in the dialog). After closing up a couple of settings, moving the mouse over the list repaints some of the category names. I'm not sure if that's a W7 thing, or a video driver thing. My video card manufacturer (AMD/ATI) has just informed me that they have reclassified my (ex-leading edge) hardware as "legacy", which means any W7 support will be best effort only, and then only after their current hardware offerings are updated and debugged. But that's hardly surprising from the company who can't actually support their own products, and whose last response to x64 driver issues was "try third-party graphics hardware or software, not ATI, and no, I'm not kidding).

That's all to report for now, I'm going through the prefs and verifying that there are no filetypes or items that Opus has taken handling ownership of, and ensuring that it's not set itself up as the explorer replacement (so far, so good).

Whoops, found another, but it might not be W7 related.

I'm setting up my file types and colours again, and if I go into Preferences|File Types, then collapse all the group headings, then expand the "System File Types" group (which is the bottom-most heading in my prefs dialog), clicking in the scrollbar area has no effect until all the collapsed headings are off-screen.

Just a minor one, I thought my eyes were finally going the way of my brain...

When I try to create a new "System" file type in Settings|File Types, the icon preview window doesn't show the full icons.

In this example, if I click "Change Icon", then browse to shell32.dll, I only see a quarter of each icon.

The bizarre thing is, as the icons are displayed in rows, across the top row, the first icon "image-let" shows the top left of that icon, the next icon to the right shows the top right of that icon, the next shows the bottom-left, the next the bottom-right, and so on.

Checking and unchecking the "Preview Large Icon Size" has no effect.

Whoops, I didn't realise that I can't edit quick-posted messages. Sorry!

WRT the icon thing, when I select a quarter-image icon in the list, the icon that is then displayed in the new filetype dialog is not the image that's displayed in the preview window, it's the actual icon that's located at that index in the dll. So while the preview may show the top left of a CD, the icon that's used is a printer (or whatever else).

I don't know if this is a W7 thing, an x64 thing, or a W7 x64 thing. Or a figment of my fevered imagination.

If you report Windows 7 issues please mention the build number as it seems a lot of these things come/go in different Win7 builds without Opus changing.

Once the Win 7 RTM comes out someone might look at them... It's probably worth just waiting for the RTM, though, to avoid all of us wasting time looking for bugs which no longer exist due to changes in Windows itself.

I am taking notes (real, physical notes that will survive a hard disk or os crash!). I'll keep taking them and figure out when I buy the OS and get to the same stage of installing apps what bugs are still here, and if I can't sort 'em out THEN I'll pop back.

[quote="leo"]If you report Windows 7 issues please mention the build number as it seems a lot of these things come/go in different Win7 builds without Opus changing.

Once the Win 7 RTM comes out someone might look at them... It's probably worth just waiting for the RTM, though, to avoid all of us wasting time looking for bugs which no longer exist due to changes in Windows itself.[/quote]For the record, from Mary-Jo Foley:

"On July 22, at precisely 4:40 p.m. ET, Microsoft announced it had released to manufacturing Windows 7 and Windows Server 2008 R2."

and

"Specifically, it’s build 7600.16385 that is the RTM version of Windows 7 and Windows Server 2008 R2."