OS Thing
XP Desktop Folder Settings
One of the main things that has irked me about XP is the fact that folder windows opened from desktop icons do not retain the position and size parameters - everything is OK then you see that classic screen shimmer and the next time you open an icon the window settings have defaulted ( I tend to like having desktop folder icons for subject groupings a bit like the old Program Manager of 3.11 days eg: Development, Utilities, Webstuff, etc).
Well so far I think the answer has been a tweak to the registry involving the Bags key.
HKEY_CURRENT-USER\Software\Microsoft\Windows\Shell\Bags
and
HKEY_CURRENT-USER\Software\Microsoft\Windows\ShellNoRoam\Bags
KB article 813711 explains the details - I set the Value to 5000 and so far it seems to work fine.
At this stage there has been no need to delete the keys (they apparently regenerate themselves) and restart windows - just making the changes as per the KB article has been sufficient.
I must say it was getting rather depressing having an OS that couldn't even remember fundamental settings for windows like position and size....
Frontpage 2003 Installer Issue
When starting Acrobat 6.0 the Frontpage installer starts running
(since FP 2003 is already installed this is a pain).
Bit of a saga once again when Microsoft is involved ..
Had a fossick around and found -
C:\Windows\Installer\ containing 4d22d.msi (this is the FP installer
dated from the install of FP2003)
I renamed the file (x4d22d.msi) and then next time Acrobat was run I got
an error where the FP installer couldn't locate FP11N.MSI
Did a search and located this file in -
N:\MSOCache\All Users\90000409-6000-11D3-8CFE-0150048383C9\ containing
FP11N.MSI
Using Programs>Accessories>System Tools>Disk Cleanup I tried to clean
out the MSOCache folder only to find that it got rid of everything
except for the FP11N.MSI, SKU117.XML and some other sub folders -
so much for the Disk Cleanup (typical CrapOS where stuff can be
installed but never cleaned out). I tried the Disk Clean again but it
indicated that the Office files were no longer there so the application
thought it had done the job but in the real world nothing had really
happened.
I renamed the MSOCache folder (xMSOCache) and still had the problem.
Where to from here then ..
Tried the great Microsoft pantheon of knowledge and found a utility
called Windows Installer Clean Up Utility (wicuu2.exe). Well the
knowledge base article stated caution when using this thing. It advised
that the installed files for the application wouldn't be removed only
the surplus install files and registry entries.
I installed and ran the utility only to find that FP 2003 had indeed
been uninstalled - on a brighter note I no longer had the problem
when starting Acrobat.
I think the concept of this utility is that it is only used to clean out
Control Panel>Add&Remove Program remnants for previous applications that
have not fully uninstalled.
So I installed FP2003 again and this time I said yes to deleting the
surplus install files (the installer gives this option). However that
would be too easy and of course the MSOCache folder was still there and
of course the installer was in the Windows\Installer folder as well (now
called 3b7ad9.msi ) - of course the problem with the Acrobat interaction
resurfaced again.
What was weird is that as I was trying the renaming technique on the
3b7ad9.msi file again when I started up Acrobat the FP CD (which I had
left in the drive) actually started spinning and then Acrobat launched
with no problem. Ever since everything is OK but why I don't know.
It seems the MSOCache folder is created by Office 2003 as a Local
Install feature for future repair/re-install of components without
requiring the CD and indeed FP2003 did exactly this. However since I
still use Office 97 and the only 2003 app I use is FP then maybe the
System Tools Disk Clean couldn't handle this (expecting other Office
2003 files/cabs to delete?).
So in summary the MSOCache folder (which in my case is on the N: drive)
could not be deleted using the MS recommendations and since they say in
BOLD letters not to use Windows Explorer to do it what was a humble user
to do .......?
.....I used Windows Explorer to rename the folder (xMSOCache) and after
a week with no problems dispatched it into the dustbin of technocracy
....
Another encounter with the "Daddy knows best" regime of MS & XP.
Win XP Pro SP1 OS moved from P3 to P4 platform
HAL type for P3 was Advanced Configuration and Power Interface (ACPI) PC
HAL type for P4 was ACPI Multiprocessor PC
Set PC to boot from CD and used the XP Pro CD
Select Setup Windows
Accept the license terms
Setup scanned for existing install of windows and located the existing copy on C:
Select the Repair option
Setup renewed the appropriate files and re-enumerated the HAL. The regional settings, etc were set up during the setup sequence as per normal.
After the final reboot the old desktop appeared and all the previously installed apps seemed to work.
The Device Manager contained c. 8 Unknown Devices entries under Other Devices
Used Uninstall option to remove the entries
Did a right click on Computer in DM and did a Scan for Hardware Changes
The devices reappeared mostly named and drivers installed as appropriate.
All in all the process seemed to work well and I didn't need to use the NTBackup that I did on the P3. As usual most of the hassle is in finding out which devices the Unknown Device entries relate to so the appropriate drivers can be supplied.