Hi Tomkovsky,
beside the fact that I would never connect myself to the internal hard EOS format neither to the SCSI connector nor to the IDE connector
:
If you want to use an external power supply for a hardrive that is installed inside the Emulator then of course you have to drill a hole into one of the covers of the expansion slots to get the HD-power cord from the external power supply into the case of the Emulator.
Another thing is:
There is no need to use the FAT32-format just on harddrives that are connected to the internal IDE bus. You can also use FAT32 on SCSI-drives.
There are two reasons to use FAT32 instead of EOS-FAT:
1. By using smaller clusters, FAT32 can handle larger hardrives more efficent than EOS-FAT. EOS-FAT is suitable for HDs of max. 20GB. Everything above 20GB -> use FAT32
I think that the maximum capacity of a HD in FAT32-format that is supported by the FAT32-implementation in EOS is about 137GB.
2. With a harddrive connected to the SCSI bus (which means that you can also connect a IDE/PATA-drive with a IDE-SCSI bridge adapter to the SCSI bus) and FAT32 installed, you can swap larger files between the PC & the Emulator. As recommended in the manual should the FAT32-HD just be connected to the PC OR the Emulator at one time. Of course is a shutdown of the Emulator & the PC for disconnecting the drive from one bus an connect it to the other bus an effort that we don't want to do very often. But this is the save option not to loose data.
Regarding the connection of a HD to the PC and to the Emulator at the same time, I think that the PC would be responsible for data-loss because it uses a cache for reading/writing from/to a harddrive and is not aware of the current status since the last "update" of the HD content. EOS in contrast to this always makes a re-scan of the HD and knows the current state of the file-system.