Gotek corruption!

Jackoland · 26 July 2017, 21:43

I have been having problems with my gotek. It has the cortex 1.5a firmware. After a period of time the adf images start having checksum errors. I have to format and copy the adfs over again (not a massive prob, I have a mirror USB folder I just re copy).

It was suggested that it might be due to poor resetting or rebooting.

Is there a recommended way to reset the Amiga and turn it off to avoid this.

I have just changed firmware to flashfloppy so I will give that a go and see how things work out.

Cheers
Rich

demolition · 26 July 2017, 22:09

Have you tried with a different USB stick? The firmware can be a bit fussy as there are many types it won't work correctly with.

UberFreak · 26 July 2017, 23:10

Are you doing many writes?
1.5a firmware is known to randomly corrupt when writing.

In any case, since there's a new open-source firmware out, I see no point in using the long abandoned "cortex" firmware.

ch40s_engineer · 27 July 2017, 12:04

Hi,

as stated on another thread, it might have to do with turning off in the wrong moment and unstable voltages. this also happens when I swap one USB stick between two Amigas. Other than that I always soft reset my Amiga and go to the adf selector, wait until it finished initialisation and then turn off the Amiga. Had no problems since then.

Superman · 27 July 2017, 22:37

Could be a simple reason that one or more of the ADF's has a virus and its spreading as you change to the next one. The bootblocks become corrupted by the virus and result in checksum 880 errors etc. Mine were doing this so I found the files which were infected with a virus and replaced them for virus free ones. No more checksum errors now.

26 July 2017, 21:43	#1
Jackoland Registered User Join Date: Jun 2014 Location: Leeds Posts: 174	Gotek corruption! I have been having problems with my gotek. It has the cortex 1.5a firmware. After a period of time the adf images start having checksum errors. I have to format and copy the adfs over again (not a massive prob, I have a mirror USB folder I just re copy). It was suggested that it might be due to poor resetting or rebooting. Is there a recommended way to reset the Amiga and turn it off to avoid this. I have just changed firmware to flashfloppy so I will give that a go and see how things work out. Cheers Rich

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Corruption - The Original	Nightfox	Games images which need to be WHDified	11	16 May 2017 20:34
HDF Corruption	BippyM	support.WinUAE	6	30 August 2016 10:03
Cannot decide which of my Amiga 500s to put the Gotek with Gotek extension board in?	turrican9	Retrogaming General Discussion	5	22 April 2016 10:39
Graphical Corruption	chocolate_boy	support.Hardware	3	27 July 2011 13:39
Graphics corruption	Minuous	support.WinUAE	9	21 July 2005 17:42

26 July 2017, 22:09	#2
demolition Unregistered User Join Date: Sep 2012 Location: Copenhagen / DK Age: 43 Posts: 4,190	Have you tried with a different USB stick? The firmware can be a bit fussy as there are many types it won't work correctly with.

26 July 2017, 23:10	#3
UberFreak Registered User Join Date: Sep 2009 Location: the world Posts: 439	Are you doing many writes? 1.5a firmware is known to randomly corrupt when writing. In any case, since there's a new open-source firmware out, I see no point in using the long abandoned "cortex" firmware.

27 July 2017, 12:04	#4
ch40s_engineer Registered User Join Date: Jan 2017 Location: Cologne Posts: 74	Hi, as stated on another thread, it might have to do with turning off in the wrong moment and unstable voltages. this also happens when I swap one USB stick between two Amigas. Other than that I always soft reset my Amiga and go to the adf selector, wait until it finished initialisation and then turn off the Amiga. Had no problems since then.

27 July 2017, 22:37	#5
Superman Super Member Join Date: Sep 2014 Location: Wakefield Age: 48 Posts: 1,334	Could be a simple reason that one or more of the ADF's has a virus and its spreading as you change to the next one. The bootblocks become corrupted by the virus and result in checksum 880 errors etc. Mine were doing this so I found the files which were infected with a virus and replaced them for virus free ones. No more checksum errors now.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)