On the other hand it is possible that although the file loading finished apparently OK, perhaps files were corrupted or some failed to get copied. Win4Lin copies the files from the CD by first mounting it under Linux and doing normal "cp". We have seen problems with damaged or dirty CDs in the past where Linux would silently not show some files and thus they would not get copied. Win4Lin has code to try to detect this situation, but flaky Linux CD drivers could possibly be causing silent failures when reading dirty or damages CDs.
You can retry loading the Windows CD (after making sure it is clean and undamaged). In order to do this you must first unload the Windows CD files previously loaded using the "/usr/bin/unloadwindowsCD" script.
You can use the Win4Lin GUI or the command "loadwindowsCD" to load the files from the Windows installation CD. This procedure copies the windows installation files into /var/win4lin/dosroot/wincabs. You can check there to see if all the Windows installation files got copied there.
When you load the Windows CD, log files are automatically created in the directory /var/win4lin/log (such as loadwindowsCD.log) This directory also has some log files created when you install the Win4Lin RPM.
When reporting to TreLOS about problems loading or installing Windows, please include copies of the log files from /var/win4lin/log.
If somehow Win4Lin did not actually get fully properly installed in the first place, the first actual noticeable problem might be that you have problems loading Windows. If you think this might be the problem, refer to the trouble shooting page about Problems installing Win4Lin. The following all assumes that Win4Lin is basically properly installed and working. To verify this, use the "dosboot" command as described in the troubleshooting page about Problems installing Win4Lin.
If the dosboot test results in an error message was about being unable to open a file named "vga.rom", that means when you previously attempted to load Windows it probably all worked except for the very last step that is supposed to be done automatically. This last step is the running of the "mkimg" command. When logged in as root, run this command, and see if it succeeds. On a reasonably modern machine, it should not take more than 15 seconds or so if it is not heavily loaded. If this command succeeds, then running "/bin/dos" should work and a DOS windows should start and give you the DOS "C>" prompt. To close this kind of DOS windows, type "quit" at the DOS prompt.
If the "mkimg" command did not succeed, or if dosboot produces some other error message, then there is some more significant problems. In this situation, looking at the log files produced when you tried to load the Windows CD might shed some light on the problem. These are in the directory "/var/win4lin/log", and are: loadwindowsCD.log, trace.dosinst and null.dosinst
When loading the Win95 CD make sure the DOS boot floppy you provide matches the version of Win95. The same goes for loading from an unbootable Win98 CD where you have to provide a bootable DOS floppy.