Okay. WTF'ery and what is all this hardware and screen shots,
seriously Al what was I doing?

Basically, I wanted to get a USB thumb drive to work on my Amiga500.

I did a fair bit of manual patching to the ANAIIS USB stack for my own pleasure
before contacting the author. He was incredibly helpful and actually shoved the
entire code base at me (Thanks!). I need to clean up my manual patching, put it
into his code and get it back to him ..or where ever it's opensourced? (not sure
about legal status so I won't post if here). Anyway, this guy was great.

Note: There was some really stupid things I did with the asm that frankly once
      I read the code in the anaiis stack I should have realised, didn't. I'm
      reliably informed that hindsight is an exact science. Will need to fix
      some of the code and re-write some of the (stupid) nasty bits in C.

Result: 
Anyway. Via manual patching, I managed to get a 2gb Verbatim USB thumb drive to
detect, partition, format, mount, read some files and write some files and dirs.

Limitations:
* It's slow. dead slooow. Read speeds were in the order of 40-50kb/s. This isn't
  bad given floppy speeds are (depending) <20kb/s.
* Write speeds are a shocker. Sometimes as low as 5kb/s. 
* SetPriority and polling needed work. A lot.
* Detection is bad. It was about 1 in 4 thumbdrive inserts that would work. 
* 2 inserts of 4, the thumbdrive ended up in the device hanging and the machine
  needing CTRL+Amiga+Amiga.
* Be slow. Stick it in.. wait upto a minute.
* Think happy enthusiastic thoughts.

Bonuses: 
* When it's detecting correctly, mounted, validated the FS. It works, just like
  any other drive. Read ..write.. concurrently.. it's all fine and rock solid.
  It's just slow. See limitations above.

Notes:
* Yeah. It's slow. addbuffers. Careful there.. if something goes wrong and you 
  addbuffers before it's settled, it can cook the entire FS. So.. once it works,
  and you can see the volume and files, then addbuffers, but don't go over 128 
  unless you like curry in your system and don't mind not being able to tell if
  the thing is busy writing or if it's locked solid and the drive is frozen.
* Just because it's been there for a while with the LED flashing, doesn't mean
  it's doing anything. When it's unstable and hasn't settled, I once copied a 
  400kb text file to it. It sat there frozen for 2hrs exercising both my 
  patience and the LED. 
* Don't trust the thumb drive LED.

Hardware I was using:
Base System           : Amiga 500 rev 6.
Hard drive Controller : GVP A590 
Hard drive            : Aztec Monster CF<->SCSI 128mb CF. 
Chip RAM              : 1mb
CPU                   : Motorola 68010
REU                   : Elbox/8
Fast RAM              : 8mb (off the Elbox/8)
Zorro RAM             : 1.5mb (mapped off the A590 (yes it has 4mb, only))
ROM                   : WB3.1 (Phoenix Switcher v1.3/2.04/3.1)
Video                 : Indivision ECS  <3 <3 <3
Expander              : A500 Clock port adapter
USB                   : Subway USB 1.1

Software:
O/S                   : AmigaOS 3.1
Compiler              : SASC 6.5
Assembler             : Devpac 2.mumblesomething

Contact:
Al. Uridium on IRC or VK2FVAX if in the Sydney area on 2m band.