"Joshua J. Kugler" wrote:
> 
> Here you go Richard.  The file is only 27K, so I didn't bother zipping it.
> Thanks for all your help.  I really appreciate it.
> 

[ For those whom I am CC'ing or BCC'ing, the background on this is that Joshua
  has been trying to install windows 98 SE with the 2.0 Eval version.  All
  goes well until the install windows phase, at which point he gets an
  "error 24".  This error 24 means that the first phase of windows installation
  failed.  I have looked at several log files and have seen that the setup
  program accesses two files not on any win98SE CD that I have: errmsg.ini
  and biosid.exe .  It then exits without any error message ]

The news is not good, I think.  It appears to me that the win98SE CD that
you have has some special copy protection feature that only lets it get
installed on the system that it came with.  Now you might say that, in
fact, you ARE installing it on the system it came with.  However, win4lin
provides a "virtual computer" environment that is generic and does not
match your specific hardware.  Thus, tricks that the setup program use to
detect the real underlying computer type will fail.

You have a couple of different options here.  The first is to procure
another copy of win9x that is generic and can be installed on any computer.
The other option is something that we don't fully support (yet) but which
might work anyway.  It is an install method known as "slurp" install.
The concept is that if you have a dual boot system where windows is 
installed on a native partition, you can install windows from that
native windows partition.

Because of the vagaries of windows configurations and disk layouts, this
approach does not always work and we didn't have enough time to work all
this out before the release of 2.0; so it is not documented.  However,
the underlying code is still there.  Since you were able to load the
windows CD and install DOS, you may be in pretty good shape.

Note that a slurp install will cause all of your windows 'C' drive to
get copied into your $HOME/win directory.  This may take up lots of room
if you have a lot of programs/fonts/etc installed.

In any event, the way to try this is to enter the following command
from an xterm shell logged in as a regular (non-root) user:
        installwindows slurp

If you have problems, you might first have to "unloadwindowsCD".

Again, this approach is not really supported yet so your mileage
might vary.  Slurp is very important because of these new copy-protected
CDs, so it will be supported in an upcoming release.

Good luck.


Richard <rwg>

-- 
Richard Bass
NeTraverse, Inc.
mailto: [EMAIL PROTECTED]
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to