Minimig on v2

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.

Don't Panic. Please wash hands.
  • Creating configuration files is known to be buggy - but saving over the top of an existing file should be working. Can you describe what happens when you try, please?

    It seems I can change and save settings if I save to the default config file on both my Sandisk cards. So I must be remembering wrong then. I was sure I had problems even saving to the default config on one of my Sandisk cards. If I try to save to any of the numbered slots I just get an error saying it cannot create the config file.

  • It seems I can change and save settings if I save to the default config file on both my Sandisk cards. So I must be remembering wrong then. I was sure I had problems even saving to the default config on one of my Sandisk cards. If I try to save to any of the numbered slots I just get an error saying it cannot create the config file.

    OK great - I will attempt to get file creation working one of these days, but as a workaround you can copy the MINMGAA.CFG file to MINMGAA1.CFG (where the "1" can be any number up to 4) - then you should be able to save to the other slots.

  • OK great - I will attempt to get file creation working one of these days, but as a workaround you can copy the MINMGAA.CFG file to MINMGAA1.CFG (where the "1" can be any number up to 4) - then you should be able to save to the other slots.

    Many thanks for the workaround. Keep up the great work

  • Is the OSD_CA01.sys file mentioned in some other posts still required? it doesnt seem to be included in the newer Minimig TC64-V2 archive. Also i am having issues with my RDB mode HDF's, they are detected in HDToolbox, i can partition them fine, save changes and the drive does show on the workbench for me to format.


    However after a reboot or restart of the TC64 the HDF drives no longer show on workbench, unless i go back into HDToolbox, read the drive config, resave changes then the drive appears for use again, but i have to do this each and every time i start the TC64/Minimig core, the only HD that works properly for me is when i partitioned my SDCard into 2 parts, 1 part for normal FAT32 to keep all the files the TC64 needs, the other partition kept as RAW for use as a "normal" drive in workbench. The "proper" drive also shows in HDToolbox, can be partitioned/formatted/etc and its changes are kept perfectly fine through reboots.


    It's just HDFs for me that arent working the same way, non RDB mode HDF arent shown/arent useable at all and the RDB mode ones vanish and need to be manually detected and saved in HDToolbox or they simply dont show and cant be used.


    Just to eliminate any issues with SFS or PFS i just left the HDF's as regular FFS and still they wont persist after reboots/restarts.. it makes things a bit more difficult for me, but thankfully the "normal" HD is working and i am currently moving files to it via mounting the FAT32 partition and copying files over, but it would be nice to have the RDB Mode HDF's persisting.

  • Is the OSD_CA01.sys file mentioned in some other posts still required? it doesnt seem to be included in the newer Minimig TC64-V2 archive.

    The OSD_CA01.sys file is the firmware for the ECS Minimig core (it's a chunk of 68k code which runs on a second TG68 CPU, handling disk emulation, menus, etc.) - the AGA core uses different firmware running on the much smaller 832 CPU (written specifically for the AGA core, and subsequently used when porting other cores.)


    Your HD problems sound very odd - I just created a very small HDF with two partitions, formatted them both as FFS and zipped the resulting file - does this mount correctly on your setup?


    Which OS / Kickstart version are you using?

  • Your Volumes Empty/Empty2 do show up and after a bit of playing around both with your HDf's and my own, ive narrowed my issue to when i successfully create the RDB HDF's, i then switch off the TC64 and hitched the HDF's to winuae to fill them up as i wanted my Workbench on a "Real" partition with Games/Work/Music/etc as hot swappable HDF's. (Various guides said make the HDFs on the real amiga side and hook them to WinUAE afterwards rather than make them in WinUAE)


    It looks like the HDF's are fine when made/partitioned on the amiga but somehow break/function weirdly as i stated in my previous post once ive filled them up via WinUAE, once i put the filled up HDF's back in the TC64 this is where its currently all going a bit wrong.


    To get around this, I am thinking that i should perhaps create/partition the HDF's, but not hook them up to WinUAE afterwards, i'm thinking now that perhaps i need to leave them be and instead move the stuff i want via the mounted FAT32 partition into the HDF's, all done via the amiga side of things so the HDF's dont break.


    I already mount SD0 specifically to move across my lha files needed to update the system (sorry i forgot to mention its OS3.2.1) so currently i think i'll do it this way to play safe, its a hell of a lot slower copying tons of files over the native way but that seems more preferable than the HDFs semi-breaking.

  • As for my next issue, not MiniMig core related exactly, perhaps..... its a common issue i think, ive had a look around on various forums but i dont want to spend heaps of cash on something like the OSSC hardware project if i can help it.


    Currently when trying native games and the likes my PAL screens are all showing as if they are NTSC with the bottoms cutoff and the top bumped down a bit rather than aligned to the top of the monitor as they should, also when using RTG mode 720x480 256 or 16bit the display works correctly but i see an occasional flickering of what looks like a copy of the top of the screen ghosted briefly on the bottom.


    This is probably because i'm using a VGA to hdmi adapter as when i plugged the TC64 into a borrowed VGA monitor there was no such issue, but using my portable HDMI monitor i get those occasional flickers as well as PAL modes looking like their forced into NTSC.


    Does anyone know of a VGA > HDMI adapter that has no such issues, there seems to be a hefty gap between cheapo adapters you see all over amazon and then a massive jump in price to the likes of the OSSC, I'd rather avoid having to buy heaps of adapters hoping 1 works well with my HDMI monitor.