mathdon wrote:I wonder if you could also help with another Win98SE problem. If you look at my last post in this thread, I was exploring a problem about the KM toolbar button not working on Win98SE that had been raised by Jerry (gplncl). I asked him to let me know the registry entry for the .xls file association (instructions given in that post) but he never replied. I think it is a further issue related to quotation marks, like your earlier ones.
If you have Excel on your Win98SE machine, could you look up that registry entry for me?
Actually, I already checked that registry entry when I first saw that issue come up in the thread. I knew I didn't have Excel installed on my Win98SE partition on that laptop, but I thought I'd check it anyway, in case it shed any light. Basically, there was a key named ".XLS" (Note: all capitals as shown, not lowercase) under the "HKEY_CLASSES_ROOT" branch, but the "(default)" entry was null, as I'd somewhat expected. I'd have posted about this, but I figured my data point wasn't helpful and figured that Jerry ('gplncl') would supply you with what you needed.
That laptop (like all my PCs) is used almost exclusively for Linux, so the Win98SE partition is pretty small and very full. But I was able to delete some stuff to free up enough disk space to squeeze a temporary install of Excel (from my "Microsoft Office 97 Small Business Edition" CD) onto that PC.
The Robman wrote:However, given that Windows and Excel are both MS programs, I would be very surprised if they let you install Excel without automatically associating it with .xls files.
I agree with Rob. And in my case, the association was indeed automatic.
mathdon wrote:First you need to look up the key HKEY_CLASSES_ROOT\.xls and see what name is given under "(Default)". In my case that is Excel.Sheet.8.
With Excel now installed, I checked the key. Just like you, my value is "Excel.Sheet.8". But, as noted above, the key name is (still) ".XLS", not ".xls" (in case that matters).
Chasing the "HKEY_CLASSES_ROOT\Excel.Sheet.8\shell\Open\command" key yields:
Code: Select all
""C:\Program Files\Microsoft Office\Office\excel.exe" /e"
The above string includes the outer "layer" of double quotes since that's how it appears in the Registry Editor window. In other words, the actual registry key export yields:
Code: Select all
[HKEY_CLASSES_ROOT\Excel.Sheet.8\shell\Open\command]
@=""C:\\Program Files\\Microsoft Office\\Office\\excel.exe" /e"
Hopefully that helps. If not, just holler my way.
mathdon wrote:And if you have Keymap Master on it, could you also tell me whether the KM toolbar button works for you?
Actually, I don't have KM on it and I've never run it at all, but I figured I'd give it a try since I now have Excel temporarily installed and I might learn something new and expand my horizons

while providing your data point....
- I ran IR.exe v8.00 and the "KM" toolbar button was desensitized (as expected). I shut down IR.exe.
- I installed KM v9.17 and ran it, did nothing, and shut it down.
- I re-ran IR.exe v8.00 and the "KM" toolbar button is now sensitized (as expected). I clicked it and it ran Microsoft Excel 97 and (after the prompt about running macros being dangerous) it opened the KM spreadsheet just fine.
I'll leave Excel installed for a while, in case further tests are needed.
mathdon wrote:I never got to the point of discovering whether he has a missing/corrupted registry entry or whether there is yet another file association issue that IR doesn't cope with.
Yeah, it sure is frustrating when people post with an issue and then don't come back with a follow-up (whether positive or negative). However, given that Jerry's 1st and 2nd posts were separated by 2 weeks, maybe he'll eventually come back to this thread with some details.
Where are you, Jerry??? 
Please provide Graham with the input he needs to help you.
On to the next issue you raised....
mathdon wrote:WagonMaster wrote: In none of those 3 setups does the 'IR.exe' main window occupy the full screen, though, so maybe the screen size/resolution thing is a "red herring".
A further thought on that issue. The main IR window is re-sizeable (as are the individual panels on the General tab, from IR8.00 on), and the size is preserved from one invocation to the next. So you can try re-sizing the window to fit the screen, to see if the issue is related to that. Incidentally, the default size of the main window, when IR is first installed, is a little less than 800x600 with the intention that it does all show on an 800x600 screen. If you've never re-sized it, does it overflow the sceen by much?
I'm not sure I'm following you completely on this one, Graham. Sorry if I'm being dense here....
As I said
in my first post about this:
WagonMaster wrote:
Regardless of how you resize the main window, the icon bar sits atop the tabs, preventing you from accessing any of them.
FYI, the screenshot from that post is with the window maximized, as seen by the "double, nested box" graphic in the upper right corner. Looking back at my post, I didn't make that clear at all -- my apologies.
I played around with it some more, still under Win98SE (800x600 LCD screen), resizing the main window to all sorts of sizes, including fullscreen, initial (non-fullscreen), and various other sizes (both larger and smaller than the default initial window size). I also resized the various panes within the main window (both horizontally and vertically). But, no matter what I did, the toolbar sits atop the tabs and the 1st row of data as shown in my screen capture.
To be thorough, I fired up IR.exe v8.00 under WinXP-SP2 on the other laptop (1280x800 LCD screen). The "toolbar sits atop tabs" problem did
not manifest itself for me under those conditions when I did this test a while back. Today, I played around with sizing the main window and the window panes as described above and, unlike 'kinggofg', I could not get it to "break" at all under WinXP-SP2.
If I've missed the intent of your post (or anything else), please let me know.
Hope some of this info proves useful, Graham. As stated earlier, just holler if you need any more info. I'll be happy to run whatever tests you need on any/all of these issues.
Regards,
Bill