Dolphin image transportation problem

Greetings,

while my kids are watching a DVD on my development machine :-)
I want to continue working on my app on my notebook.

So here comes another one of those long posts of mine ...


So I zip my development tree up and copy the stuff over
from NT under VMware on a linux box to Win2K on my Notebook,
extract the stuff and double click the image .... and
receive an error message that Dolphin is "Unable to open the
image file ..." after which Dolphin exits.

So I try to open my default image on this box and get
the same message, but for the image I tried first.

Well, having seen those opening problems on Windoze before,
I search for "Dolphin" in the Registry and find
HKCU\Software\Classes\applications\Dolphin.exe\shell\Open\command
with a nice readable command line and an encrypted version:

"C:\Programme\Dolphin Smalltalk 4.0\Dolphin.exe" -open"%1"

Just for fun, I modify the command line to
... -open "%1"

and hack the blank into the crypted version, too.

After this, I still get a warning ("Unable to open" only)
but the image opens and is in the saved state.

If I quit and open the image via the cached version
(link to Dolphin in the Start menu), I get no warning.


Another thing that is going to be interesting is the following:
I have left a (saved) Workspace open before doing the snapshot.
After opening it, I have the *same* state as on the other machine.
With a totally wrong file name in the caption of the workspace
window. Let's see what happens when I hit save ... a windows message
box appears telling me that the path can't be found, as it is in
German, it originates with the system and not by Dolphin, I guess.

Are there any other issues that might complicate transporting
a snapshot between two machines?

Regards,
Stefan

Stefan Schmiedl
EDV-Beratung, Programmierung, Schulung
Loreleystr. 5, 94315 Straubing, Germany
Tel. (0 94 21) 74 01 06
Public Key: http://xss.de/stefan.public

shhhh ... I can't hear my code!

On 23 Jan 2002 18:51:56 GMT, Stefan Schmiedl <[hidden email]> wrote:
> Greetings,
>
> while my kids are watching a DVD on my development machine :-)
> I want to continue working on my app on my notebook.
>

Now that the kids are in bed, I checked out my normal machine
and found that I introduced another bug which almost completely
killed the first :-)

it is not a Dolphin problem, but (of course :-) was caused
by the usual combination of Windows registry evil and a careless user.
You see, I have a copy of PaintShop Pro running on the notebook, which
was installed after Dolphin. And registered .img-files as some arcane
graphics format to itself. Which I changed back, messing something
up during the process.

how come things like that never happen to me on linux?

btw: has anybody tried running dolphin with wine or some other
emulator besides vmware?

bye,
stefan

--
Stefan Schmiedl
EDV-Beratung, Programmierung, Schulung
Loreleystr. 5, 94315 Straubing, Germany
Tel. (0 94 21) 74 01 06
Public Key: http://xss.de/stefan.public

shhhh ... I can't hear my code!