No i must aplogise to you, I had not had coffe before that post, not that that is an excuse, rather just the cause of my bad reply.
I also didnt really form the reply overly well, as i was doing other things at the time, and wrote it over maybe an hour, I honestly read it now and would have replied to myself with "F U 2 Mr DaveC, U obnoxius git."

Just as a matter of interest incase someone has opne this is how i worked out what slot things went into

Code:
alias ex {
  var %size = 100 
  hfree -sw ex | hmake -s ex %size
  var %i = $calc(%size * 100) | while (%i) { hadd ex $+(itemname,%i) %i | dec %i }
  exc
  var %i = 1, %m = $calc(%size * 100), %s = 0, %l = 0, %c
  while (%i <= %m) {
    var %c = $line(@ex,%i) | if (%c < %l) { inc %s }
    hadd ex $+(itemname,%c) $+(itemname,%c) $+(Slot,%s)
    var %l = %c
    inc %i
  }
  exc
}
alias exc { hsave -sn ex ex.txt | window -c @ex | window -e @ex | loadbuf @ex ex.txt }


First run /EX this might take a second or two, the resulting @EX window shows the itemnameN on the itemnames and the slot they are in.
Next you simple do a /hadd ex itemname_of_your_own itemname_of_your_own using itemdata the same as the itemname ie: /hadd ex apple apple
Lastely run /EXC this makes a new @EX window find the itemname_of_your_own in the list and its the slot listed on the line above.

* all it does is throw a big pile of itemname1 to N into a hashtable, then saves the data to a file, then to a window, it then works its way down that window baing the increment of the slot number loosly on the princible that the last number in the current slot well be higher than the first number in the next slot ie: ...
slot0 - 123
slot0 - 567
slot0 - 999
slot1 - 256
slot1 - 333
etc

All the /exc does is redisplay the window with the "APPLE" entery also in it stuck at the end of what ever slot it fell into.