[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] Daily mintv4e.prg
Heinz Schmidt wrote:
I noticed that after every attempt to boot from CF the
C:/mint/1-18-cur directory is empty and the file system is corrupted. So
may be the described problem is not a mint issue but a file system issue.
Unfortunately, this happens very frequently.
FireTOS' FAT driver is unreliable on big partitions, and the problem is
even worse with EmuTOS. However, FreeMiNT's FAT driver (NEWFATFS) seems
to be rock solid, I never experienced corruption with it.
So, if you have a clean filesystem, there are good chances that FireTOS
will correctly load mintv4e.prg, then NEWFATS will be used for all the
further operations and no corruption will occur.
Personally, I always keep a clean image of my whole MiNT setup in a
folder on my Windows PC. I often check the CompactFlash filesystem using
the chkdsk tool on Windows. When something is wrong, I fix the
filesystem using chkdsk, then I delete everything from the CompactFlash
drive and I copy again the backuped MiNT setup to it.
Now the FireBee starts up but every mouse move
leads to screen output which destroys the desktop.
I never experienced that.
> Also remember to set boot bpp to 8bit, otherwise boot speed is too slow.
Good point, I did not change anything on the FireBee configuration. How
I change the colour depth? Using Bootconf?
It can be changed using XCONTROL.ACC and FIRECONF.CPX.
You should ask the ACP mailing list for that.
--
Vincent Rivière