You will not be able to post if you are still using Microsoft email addresses such as Hotmail etc
See here for more information viewtopic.php?f=20&t=7296
See here for more information viewtopic.php?f=20&t=7296
DO NOT USE MOBILE / CGNAT DEVICES WHERE THE IP CHANGES CONSTANTLY!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
330 disable function bug
Moderators: terriblefire, Terriblefire Moderator
Re: 330 disable function bug
Hmm this is weird. My CD ROM won't work with or without the card now... on both of my consoles.
The disbale function works correctly, but no idea what's up with the CD.
The disbale function works correctly, but no idea what's up with the CD.
Re: 330 disable function bug
I got the CD ROM to work again, and now I can confirm it fails to work in 020 mode only.
-
terriblefire
- Admin sponsor

- Posts: 5670
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: 330 disable function bug
OK i need to spend time on this but the 360 is on the rig at the moment.. Maybe i need another rig.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: 330 disable function bug
hi Stephen,
when do you think you could look into this? possibly together with the nvram issue? waiting for a complete TF330..
thank you
when do you think you could look into this? possibly together with the nvram issue? waiting for a complete TF330..
thank you
-
terriblefire
- Admin sponsor

- Posts: 5670
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: 330 disable function bug
I’m not planning to do any 330 work until August due to holidays etc
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: 330 disable function bug
I updated the firmware to the version I got from Mark two days ago. He said this issue has been fixed in that firmware, but I still have the same problem (CD32 will not boot when the TF330 is disabled).
-
terriblefire
- Admin sponsor

- Posts: 5670
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: 330 disable function bug
The issue with the nvram is fixed.
The disable issue is still present. I’ll fix this eventually.
I suspect I’ll figure it out while working on the TF360
The disable issue is still present. I’ll fix this eventually.
I suspect I’ll figure it out while working on the TF360
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: 330 disable function bug
Thanks, looking forward to the fix!terriblefire wrote: Thu Sep 19, 2019 3:31 pm The issue with the nvram is fixed.
The disable issue is still present. I’ll fix this eventually.
I suspect I’ll figure it out while working on the TF360
Re: 330 disable function bug
same here!MickGyver wrote: Thu Sep 19, 2019 5:50 pmThanks, looking forward to the fix!terriblefire wrote: Thu Sep 19, 2019 3:31 pm The issue with the nvram is fixed.
The disable issue is still present. I’ll fix this eventually.
I suspect I’ll figure it out while working on the TF360![]()
Re: 330 disable function bug
...and same here also!... 
