Re: [MiNT] Daily mintv4e.prg

[Paul Wratt <paul.wratt@gmail.com>]

this might be a good time to add a "clean/plain" mint.cnf for
coldfire, and possibly sh/bat scripts that automate the folder builds
(to boot a FireBee in this case), say in a "scripts" and "conf"
folders in the nightly builds

both of these will save a lot of time (and head aches for some users),
can be expanded (or added) for other (standard) systems, and will give
people a higher reference point when things go wrong.

I have no problem is helping with creating or supplying scripts for
plain aranym, arfos, easymint (for aranym). scripts that will let you
know what else you need (ie auto folder) and check if they are in the
proper structure/order. NOTE: as far as I know, a script to handle an
easymint setup for aranym would also work for a "clean" falcon (ie
auto folder boot), which may also be the case for the FireBee

It is good to see an almost complete CF build for FireBee users, big
thanks to the efforts of everyone involved

Cheers

Paul

2011/7/16 Vincent Rivière <vincent.riviere@freesbee.fr>:
> 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
>
>
>