fritz.mueller

hi, i am not absolutely sure if I understood you correct. you used two different cd rom drives? and it works with one of them? fdimples started from hd should support the cd and install everything that is on cd - or the programs that you have chosen. it can also remove programs. but even the life cd is only a part, there is also a bonus cd available that you can install, eventually in parts - with fdimples. as a next you could install additional programs via internet and fdnpkg. but this is not so...

hi, i think we come closer. if i remember right, the first cd rom drives came up in ca. 1993 - and they sometimes had exotic cd rom drivers for each different cd rom. and the first cd rom drives supported only (ca.) 640 mb, i cdirc instead of 700 mb. and you had to jumper them as master/slave on the backside of the cd rom. so it would be helpful to see what happens if you simply copy the whole content of the cd on the hd, e.g. to a folder, test with xcopy or doszip. if there are problems, fdimples...

Hi, try to install a small installation first, as the big one writes the boot system at the end of installation, so the first installed files will not be bootable. but of course you can also run a sys c: from the cd if you run it from live cd.. If this works, you can first of all execute fdisk to see how big the partition is and if it is fat 16 or fat32. i assume that it is fat16 only as fd may have problems with ezdrive. when i am correct, try to run fdisk over the rest of the hd, so that we can...

I just ran a test on a real (working) diskette and had no problems. So I kept it as it was. AI said that a fix would be to set "assert(0);" in blkcache.c, line 322 to "rem".

Would also work with the help of AI. But I am no programmer, I hope I can find a programmer to check all this.

I also asked Google AI and she gave me a solution that works, but I am no programmer, so it can be sure that it added other bugs and will have to give it to a programmer for test purposes.

Today I asked Google AI and this is the response: I noticed that chkdsk does not display a creation date if the volume has no label. After analyzing the FAT file system structure, it turns out this is not a bug in chkdsk, but a technical characteristic of the FAT design. Technical Explanation: The "Volume Creation Date" is not stored in the Boot Sector (BPB) alongside the Serial Number. Instead, it is stored as the modification timestamp of the Volume Label entry within the Root Directory. The Volume...

@jerome: This is a quick and dirty italian translation made by AI. Please check. A first look at it showed me that it seems to be ok. Compare it with the screenshot above.