Hmmmmmmmm. This sounds vaguely familiar.
At what point in the installation did you run the realupd.bat program? I
seem to recall that this has to be run after the install of Isodat, but
*before* you reboot. I think that there's some stuff that Isodat has
that conflicts with Real32 as delivered.
If that's the case, then the trick is how to get back into Real32 so
that you can either do the realupd or re-install isodat. It may be that
you can just boot from the real32 startup disk and then run from that
while you do the realupd routine. Alternatively, both real32 and
isodat-install are pretty dumb, and just tend to overwrite files, so
maybe just re-load real32 and isodat on top of what's already there,
without even trying to remove anything first (this avoid the problem of
in-advertently removing MS-DOS or Win2000 files.
Hope that this helps... or triggers someone else's thoughts.
Carl G. Johnson
Research Associate III
Woods Hole Oceanographic Institution