Hi Andy,
Something is not right in G'ville. I have a sound backup, so there's no
panic (at least not yet<g>). This could be a hardware problem (though I'd
expect that to be less predictable than what I'm seeing, unless it's the
hard disk, which will get tested shortly), or perhaps a case of DLL hell.
As **completely** unfair as this is, I'll mention that I noticed this
problem very shortly after installing and playing with Bot-Kit. At first I
thought that the spirit.ocx might have stomped on some memory and corrupted
my image. Then I tried a known good image on this box and got similar
results. That makes it look like the OS, hardware, or Dolphin runtimes. Is
there any chance that the Bot-Kit MSI altered something in the runtimes?
One thing that strikes me as odd about it is the large number of components.
The file table looks harmless though.
On the more concrete front, I downloaded the Dolphin MSI again and started
rebuilding images. If I'm doing everything correctly, it's not at PL1; does
that sound right? Either way, it was useful because I tried something that
leads to a suggestion. I did my image preparation and then ran live update;
on seeing the help, I realized that I had done it backwards, and should have
patched the starting image. It seemed that I could save a step by capturing
the patch in a file. On trying to load that file into a fresh image, I
found that it wants to talk to your web server. There are times (dog and
pony shows, ISP down time) when this could be a problem. If possible, it
would be nice for the patches to be self-contained just in case, or perhaps
pop up a message box that says something like "sample xyz won't be patched -
proceed?". In a pinch of course, I could probably hack a solution, and in
this case I just dialed in again and let it do what it wanted.
Re the Dolphin MSI: what does the repair option do? Let's suppose that a
file corruption is the cause of my problem; should repairing Dolphin fix it?
How does it compair with uninstalling and reinstalling. Finally, what
should I do on the "other machine"? After rebuilding my image with the
revised Dolphin, which I understand has an updated VM, what should I do to
propagate that to other machines that I use?
Have a good one,
Bill
--
Wilhelm K. Schwab, Ph.D.
[hidden email]
Locked
