Re: [M100] Bar code reader with REX

[Peter Vollan]

Barcode Battler for the Model T!


On 9 March 2018 at 23:16, Willard Goosey  wrote:
> On Fri, 09 Mar 2018 15:40:27 +
> Gregory McGill  wrote:
>
>> Thanks for this I spent an hour the other day trying to find out what
>> files I needed and make it work finally did get upc's reading
>
> You're welcome! :-)
>
> And congratulations! This is hardware that takes some skill to use!
>
> Willard
> --
> Willard Goosey  goo...@sdc.org
> Socorro, New Mexico, USA
> I search my heart and find Cimmeria, land of Darkness and the Night.
>   -- R.E. Howard

Re: [M100] Bar code reader with REX

[Willard Goosey]

On Fri, 09 Mar 2018 15:40:27 +
Gregory McGill  wrote:

> Thanks for this I spent an hour the other day trying to find out what
> files I needed and make it work finally did get upc's reading

You're welcome! :-)

And congratulations! This is hardware that takes some skill to use!

Willard
-- 
Willard Goosey  goo...@sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard

Re: [M100] Bar code reader with REX

[Willard Goosey]

On Fri, 9 Mar 2018 09:26:28 -0500
Anthony Coghlan  wrote:

> Thanks, Willard!  I managed to read the BCR files from the original
> tape (amazingly durable) into the Model 100 with my “new” non-Radio
> Shack BCR. 

You're welcome! :-)

>It works, though I am still amazed at how sensitive the
> reading is to so many factors including just basic spacing and
> contrast of the bar pattern, it seems.  Maybe I’m not “doing” it
> correctly.  Definitely still learning. My read reliability seems
> fairly low overall except for some bar codes. Can bar codes have
> changed and gotten so much more “compact” and challenging to read
> since the mid-1980s?  It’s not something I noticed back then...  :)

Yes, it's pretty fussy about the angle the wand is held at, and a big
factor is how fast the wand is swiped. You have to swipe really fast!

I'll be honest, when I got a Tandy wand and the software, I thought the
wand was broken because I couldn't get it to work at all... So I got a
second one (this one came with the docs). Turns out they both work...
But I would never have gotten them to work without the known-as-good
swipable samples in the book. I practiced on them until I learned to
get consistant reads.

UPC hasn't really changed(*), but a lot of samples aren't
high-enough-contrast for the Tandy wand to read. I think the smaller
denser codes on various things aren't UPC and I don't know/care enough
to try to identify them for reading

> REX is on my M102.  I’m eager to try your REX BCR image and the
> additional, recent driver files.

REX is awesome!

(*)I think there is actually a newer UPC standard but I don't think it
actually is used much?

Willard
-- 
Willard Goosey  goo...@sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard

Re: [M100] Bar code reader with REX

[Anthony Coghlan]

Thanks, Willard!  I managed to read the BCR files from the original tape
(amazingly durable) into the Model 100 with my “new” non-Radio Shack BCR.
It works, though I am still amazed at how sensitive the reading is to so
many factors including just basic spacing and contrast of the bar pattern,
it seems.  Maybe I’m not “doing” it correctly.  Definitely still learning.
My read reliability seems fairly low overall except for some bar codes.
Can bar codes have changed and gotten so much more “compact” and
challenging to read since the mid-1980s?  It’s not something I noticed back
then...  :)

REX is on my M102.  I’m eager to try your REX BCR image and the additional,
recent driver files.

Best wishes,
Anthony




On Friday, March 9, 2018, Willard Goosey  wrote:

> On Sat, 3 Mar 2018 06:11:45 -0500
> Anthony Coghlan  wrote:
>
> > Thanks, Willard - I'll give those suggestions a try.  Won't be this
> > weekend, unfortunately - bunch of other things going on - but this
> > information will be very helpful.  I like the idea of a BCR RAM
> > image.  I can use it to keep the drivers, programs, and all my
> > "valuable" inventory data!
> >
> Well when you get to it, http://www.sdc.org/~goosey/m100/allbcr.zip has
> a REX RAM image of all the BCR code, and also, as seperate files, the
> original drivers and the recently uploaded additional drivers.
>
> Willard
> --
> Willard Goosey  goo...@sdc.org
> Socorro, New Mexico, USA
> I search my heart and find Cimmeria, land of Darkness and the Night.
>   -- R.E. Howard
>

Re: [M100] Bar code reader with REX

[Willard Goosey]

On Sat, 3 Mar 2018 06:11:45 -0500
Anthony Coghlan  wrote:

> Thanks, Willard - I'll give those suggestions a try.  Won't be this
> weekend, unfortunately - bunch of other things going on - but this
> information will be very helpful.  I like the idea of a BCR RAM
> image.  I can use it to keep the drivers, programs, and all my
> "valuable" inventory data!
>
Well when you get to it, http://www.sdc.org/~goosey/m100/allbcr.zip has
a REX RAM image of all the BCR code, and also, as seperate files, the
original drivers and the recently uploaded additional drivers.

Willard
-- 
Willard Goosey  goo...@sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard

Re: [M100] Bar code reader with REX / M100 Digest, Vol 87, Issue 2

[Gregory McGill]

picked up two for 13ea off ebay, work great

Greg

On Fri, Mar 2, 2018 at 8:50 AM, Gregory McGill <arcadeshop...@gmail.com>
wrote:

> they are 29$ new on newegg
>
> On Fri, Mar 2, 2018 at 4:49 AM, Anthony Coghlan <coghl...@gmail.com>
> wrote:
>
>> Thanks, Peter. I think I’m going to try the barcode reader you use if I
>> can get it on eBay cheaply, as it may be more reliable anyway.  Perhaps I
>> have to try loading the driver and program with REX temporarily disabled as
>> an experiment.  I suspect a conflict in memory and don’t otherwise know how
>> to resolve that.
>>
>> Best wishes,
>> Anthony
>>
>>
>>
>> On Friday, March 2, 2018, Peter Noeth <petern0...@gmail.com> wrote:
>>
>>> I don't have a REX in my M102, but I have been using the BCR to do
>>> "pantry" and "wine cellar" inventory. Both are in the basement, so are not
>>> readily accessible when one wants to know what is down there. I am not
>>> using the Radio Shack wand, but instead am using a UniTech
>>> MS120-NTCB00-SG "industrial strength" wand. It is "plug-in" compatible with
>>> the RS wand, and has a sapphire tip that doesn't abrade the barcode labels
>>> and keeps dust out of the wand. It also has better "dynamic range" so has
>>> no problems reading low contrast barcodes or ines in color. I am using the
>>> sample "Simple Inventory" program (with some modifications) that came with
>>> the RS Barcode Reader package. I read the "database" file into Excel
>>> and keep a printout in the kitchen. The program works well, and barcode
>>> reads are quite reliable once you get used to the swiping speed needed.
>>>
>>> As to your program conflicts, problem with many of the early computers
>>> with "operating systems" supplied by Microsoft, is the RAM driver concept
>>> is limited in practical use. Microsoft intended the RAM driver facility to
>>> patch a ROM driver that may have bugs or add additional planned system
>>> expansion (like the DVI, Bar Code Reader, TDD, Option ROM, etc.). Later
>>> third party developers who had a product that used their own RAM driver all
>>> seemed to locate them in the same address in memory (top of available RAM,
>>> the logical place to put it). This creates memory conflicts. Especially in
>>> computers using the Intel 8080/8085 processors that do not support
>>> "relative" addressing. Without relative addressing, the user cannot move a
>>> driver to a different starting address in memory without recompiling it
>>> first, and since the user does not get a copy of the source code, he is
>>> usually out of luck.
>>>
>>> There were a few attempts using programs that would read the code of the
>>> driver and attempt to find all of the JMP and CALL instructions and patch
>>> them directly to a new base starting address, but it was not always
>>> successful, as often times the driver would contain inline data bytes that
>>> would confuse the conversion program. These programs usually worked on
>>> computers using the Z80 processors, since it did support relative
>>> addressing.
>>>
>>> Regards,
>>>
>>> Peter
>>>
>>> 
>>>
>>> 
>>>
>>> Message: 14
>>> Date: Fri, 2 Mar 2018 00:57:07 -0500
>>> From: Anthony Coghlan <coghl...@gmail.com>
>>> To: "m...@bitchin100.com" <m...@bitchin100.com>
>>> Subject: Re: [M100] Bar code reader with REX
>>> Message-ID:
>>> <canesrqv93k+ksufjam+a-lgikozpwwdubcgget4u-uk2ogz...@mail.gm
>>> ail.com>
>>> Content-Type: text/plain; charset="utf-8"
>>>
>>> Yes, that was the drive belt I used also if I recall, made by Russell
>>> Industries.  I can?t find my old purchase info from eBay, but it was
>>> about
>>> $9 at the time.  (I think Brian mentioned that price as well.)  It was so
>>> nice to see the drive come to life!
>>>
>>> Best wishes,
>>> Anthony
>>>
>>>
>>> All on the list:  any tips on reliably using the bar code reader?
>>> Thanks.
>>> I?m threatening to inventory our pantry if I can get it working, though
>>> my
>>> wife doesn?t think that?s such a practical application...  :)
>>>
>>> 
>>>
>>>
>>>
>

Re: [M100] Bar code reader with REX

[Gregory McGill]

just tested mine with the new wands i got off ebay with rex and quad works
fine

Greg

On Sat, Mar 3, 2018 at 3:11 AM, Anthony Coghlan  wrote:

> Thanks, Willard - I'll give those suggestions a try.  Won't be this
> weekend, unfortunately - bunch of other things going on - but this
> information will be very helpful.  I like the idea of a BCR RAM image.  I
> can use it to keep the drivers, programs, and all my "valuable" inventory
> data!
>
> I was able to get the alternative barcode reader suggested elsewhere in
> the thread on eBay for about $20 used.  Sapphire tip, able to read reliably
> in a wider range of circumstances, and still quite sleek-looking - should
> be a good thing.
>
> Best wishes,
> Anthony
>
>
>
> On Sat, Mar 3, 2018 at 2:10 AM, Willard Goosey  wrote:
>
>> On Fri, 2 Mar 2018 15:46:55 -0500
>> Anthony Coghlan  wrote:
>>
>> (OK on a real keyboard now! :)
>>
>> > Willard, thanks for the confirmation that it’s not something inherent
>> > to trying to use REX and BCR at the same time.  That would be sad,
>> > because I like my REX...
>>
>> I agree, REX is awesome! The BCR is... kind of a neat toy? But yes they
>> work fine together for me. I've got a RAM image named BCR with all the
>> goodies!
>>
>> > I think I got the driver off Club 100 and
>> > transferred It with MComm.  I have the original cassette, too, but
>> > haven’t tried it.
>>
>> I know the versions in the UPS directory work, are those the ones
>> you're using?
>>
>> > Poke and reboot - could you tell me more, so I’ll get it right..?  :)
>> >  Thanks.  Otherwise, I’d just end up doing CALL 63012 a couple of
>> > times, perhaps not the desired / required steps.  Thanks again.
>>
>> Ahh... After a crash and reboot, go into BASIC:
>> POKE 62975,201
>>
>> then power cycle. This clears the timer hook REX uses.
>> Go into BASIC again and:
>> CALL 63012
>>
>> this will bring up REXMGR.
>>
>> (this is all in the REX wiki on bitchin100).
>>
>> (wow I had to look this up, it's been a couple of months since I
>> crashed the M100! Takin' a little break from SmallC-85 to explore RISC
>> OS :)
>>
>>
>> Hope this helps,
>> Willard
>> --
>> Willard Goosey  goo...@sdc.org
>> Socorro, New Mexico, USA
>> I search my heart and find Cimmeria, land of Darkness and the Night.
>>   -- R.E. Howard
>>
>
>

Re: [M100] Bar code reader with REX

[Anthony Coghlan]

Thanks, Willard - I'll give those suggestions a try.  Won't be this
weekend, unfortunately - bunch of other things going on - but this
information will be very helpful.  I like the idea of a BCR RAM image.  I
can use it to keep the drivers, programs, and all my "valuable" inventory
data!

I was able to get the alternative barcode reader suggested elsewhere in the
thread on eBay for about $20 used.  Sapphire tip, able to read reliably in
a wider range of circumstances, and still quite sleek-looking - should be a
good thing.

Best wishes,
Anthony



On Sat, Mar 3, 2018 at 2:10 AM, Willard Goosey  wrote:

> On Fri, 2 Mar 2018 15:46:55 -0500
> Anthony Coghlan  wrote:
>
> (OK on a real keyboard now! :)
>
> > Willard, thanks for the confirmation that it’s not something inherent
> > to trying to use REX and BCR at the same time.  That would be sad,
> > because I like my REX...
>
> I agree, REX is awesome! The BCR is... kind of a neat toy? But yes they
> work fine together for me. I've got a RAM image named BCR with all the
> goodies!
>
> > I think I got the driver off Club 100 and
> > transferred It with MComm.  I have the original cassette, too, but
> > haven’t tried it.
>
> I know the versions in the UPS directory work, are those the ones
> you're using?
>
> > Poke and reboot - could you tell me more, so I’ll get it right..?  :)
> >  Thanks.  Otherwise, I’d just end up doing CALL 63012 a couple of
> > times, perhaps not the desired / required steps.  Thanks again.
>
> Ahh... After a crash and reboot, go into BASIC:
> POKE 62975,201
>
> then power cycle. This clears the timer hook REX uses.
> Go into BASIC again and:
> CALL 63012
>
> this will bring up REXMGR.
>
> (this is all in the REX wiki on bitchin100).
>
> (wow I had to look this up, it's been a couple of months since I
> crashed the M100! Takin' a little break from SmallC-85 to explore RISC
> OS :)
>
>
> Hope this helps,
> Willard
> --
> Willard Goosey  goo...@sdc.org
> Socorro, New Mexico, USA
> I search my heart and find Cimmeria, land of Darkness and the Night.
>   -- R.E. Howard
>

Re: [M100] Bar code reader with REX

[Willard Goosey]

On Fri, 2 Mar 2018 15:46:55 -0500
Anthony Coghlan  wrote:

(OK on a real keyboard now! :)

> Willard, thanks for the confirmation that it’s not something inherent
> to trying to use REX and BCR at the same time.  That would be sad,
> because I like my REX... 

I agree, REX is awesome! The BCR is... kind of a neat toy? But yes they
work fine together for me. I've got a RAM image named BCR with all the
goodies!

> I think I got the driver off Club 100 and
> transferred It with MComm.  I have the original cassette, too, but
> haven’t tried it.

I know the versions in the UPS directory work, are those the ones
you're using?

> Poke and reboot - could you tell me more, so I’ll get it right..?  :)
>  Thanks.  Otherwise, I’d just end up doing CALL 63012 a couple of
> times, perhaps not the desired / required steps.  Thanks again.

Ahh... After a crash and reboot, go into BASIC:
POKE 62975,201

then power cycle. This clears the timer hook REX uses.
Go into BASIC again and:
CALL 63012

this will bring up REXMGR.

(this is all in the REX wiki on bitchin100).

(wow I had to look this up, it's been a couple of months since I
crashed the M100! Takin' a little break from SmallC-85 to explore RISC
OS :)


Hope this helps,
Willard
-- 
Willard Goosey  goo...@sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
  -- R.E. Howard

Re: [M100] Bar code reader with REX

[Fugu ME100]

It might be best to simply do a cold reboot  make sure there is nothing hanging 
around in memory to cause problems.Then start the REX and BCR drivers.

There are some applications that will not work with REX because of how it 
operates.

From: M100 
<m100-boun...@lists.bitchin100.com<mailto:m100-boun...@lists.bitchin100.com>> 
on behalf of Anthony Coghlan <coghl...@gmail.com<mailto:coghl...@gmail.com>>
Reply-To: <m...@bitchin100.com<mailto:m...@bitchin100.com>>
Date: Friday, March 2, 2018 at 12:46 PM
To: "m...@bitchin100.com<mailto:m...@bitchin100.com>" 
<m...@bitchin100.com<mailto:m...@bitchin100.com>>
Subject: Re: [M100] Bar code reader with REX

Willard, thanks for the confirmation that it’s not something inherent to trying 
to use REX and BCR at the same time.  That would be sad, because I like my 
REX...  I think I got the driver off Club 100 and transferred It with MComm.  I 
have the original cassette, too, but haven’t tried it.

Poke and reboot - could you tell me more, so I’ll get it right..?  :)  Thanks.  
Otherwise, I’d just end up doing CALL 63012 a couple of times, perhaps not the 
desired / required steps.  Thanks again.

Best wishes,
Anthony





On Friday, March 2, 2018, Willard Goosey 
<goo...@sdc.org<mailto:goo...@sdc.org>> wrote:
sorry losey on screen keyboard here..

BCR+REX work fine on my m100.

Sugest you reload the .CO files... known good versions are on club100

REX doesn't leave anything in ram the bcr drivers dont mess with rom.

when a rexed m100 crashes it is normal to boot up with the lasr rom selected, 
do the poke & reboot dance to get rexmgr back

willard


Sent from my Galaxy Tab® A

Re: [M100] Bar code reader with REX

[Anthony Coghlan]

Willard, thanks for the confirmation that it’s not something inherent to
trying to use REX and BCR at the same time.  That would be sad, because I
like my REX...  I think I got the driver off Club 100 and transferred It
with MComm.  I have the original cassette, too, but haven’t tried it.

Poke and reboot - could you tell me more, so I’ll get it right..?  :)
 Thanks.  Otherwise, I’d just end up doing CALL 63012 a couple of times,
perhaps not the desired / required steps.  Thanks again.

Best wishes,
Anthony





On Friday, March 2, 2018, Willard Goosey  wrote:

> sorry losey on screen keyboard here..
>
> BCR+REX work fine on my m100.
>
> Sugest you reload the .CO files... known good versions are on club100
>
> REX doesn't leave anything in ram the bcr drivers dont mess with rom.
>
> when a rexed m100 crashes it is normal to boot up with the lasr rom
> selected, do the poke & reboot dance to get rexmgr back
>
> willard
>
>
> Sent from my Galaxy Tab® A
>

Re: [M100] Bar code reader with REX

[Willard Goosey]

sorry losey on screen keyboard here..
BCR+REX work fine on my m100.
Sugest you reload the .CO files... known good versions are on club100
REX doesn't leave anything in ram the bcr drivers dont mess with rom.
when a rexed m100 crashes it is normal to boot up with the lasr rom selected, 
do the poke & reboot dance to get rexmgr back
willard

Sent from my Galaxy Tab® A
null

Re: [M100] Bar code reader with REX / M100 Digest, Vol 87, Issue 2

[Gregory McGill]

they are 29$ new on newegg

On Fri, Mar 2, 2018 at 4:49 AM, Anthony Coghlan <coghl...@gmail.com> wrote:

> Thanks, Peter. I think I’m going to try the barcode reader you use if I
> can get it on eBay cheaply, as it may be more reliable anyway.  Perhaps I
> have to try loading the driver and program with REX temporarily disabled as
> an experiment.  I suspect a conflict in memory and don’t otherwise know how
> to resolve that.
>
> Best wishes,
> Anthony
>
>
>
> On Friday, March 2, 2018, Peter Noeth <petern0...@gmail.com> wrote:
>
>> I don't have a REX in my M102, but I have been using the BCR to do
>> "pantry" and "wine cellar" inventory. Both are in the basement, so are not
>> readily accessible when one wants to know what is down there. I am not
>> using the Radio Shack wand, but instead am using a UniTech
>> MS120-NTCB00-SG "industrial strength" wand. It is "plug-in" compatible with
>> the RS wand, and has a sapphire tip that doesn't abrade the barcode labels
>> and keeps dust out of the wand. It also has better "dynamic range" so has
>> no problems reading low contrast barcodes or ines in color. I am using the
>> sample "Simple Inventory" program (with some modifications) that came with
>> the RS Barcode Reader package. I read the "database" file into Excel
>> and keep a printout in the kitchen. The program works well, and barcode
>> reads are quite reliable once you get used to the swiping speed needed.
>>
>> As to your program conflicts, problem with many of the early computers
>> with "operating systems" supplied by Microsoft, is the RAM driver concept
>> is limited in practical use. Microsoft intended the RAM driver facility to
>> patch a ROM driver that may have bugs or add additional planned system
>> expansion (like the DVI, Bar Code Reader, TDD, Option ROM, etc.). Later
>> third party developers who had a product that used their own RAM driver all
>> seemed to locate them in the same address in memory (top of available RAM,
>> the logical place to put it). This creates memory conflicts. Especially in
>> computers using the Intel 8080/8085 processors that do not support
>> "relative" addressing. Without relative addressing, the user cannot move a
>> driver to a different starting address in memory without recompiling it
>> first, and since the user does not get a copy of the source code, he is
>> usually out of luck.
>>
>> There were a few attempts using programs that would read the code of the
>> driver and attempt to find all of the JMP and CALL instructions and patch
>> them directly to a new base starting address, but it was not always
>> successful, as often times the driver would contain inline data bytes that
>> would confuse the conversion program. These programs usually worked on
>> computers using the Z80 processors, since it did support relative
>> addressing.
>>
>> Regards,
>>
>> Peter
>>
>> 
>>
>> 
>>
>> Message: 14
>> Date: Fri, 2 Mar 2018 00:57:07 -0500
>> From: Anthony Coghlan <coghl...@gmail.com>
>> To: "m...@bitchin100.com" <m...@bitchin100.com>
>> Subject: Re: [M100] Bar code reader with REX
>> Message-ID:
>> <canesrqv93k+ksufjam+a-lgikozpwwdubcgget4u-uk2ogz...@mail.gm
>> ail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Yes, that was the drive belt I used also if I recall, made by Russell
>> Industries.  I can?t find my old purchase info from eBay, but it was about
>> $9 at the time.  (I think Brian mentioned that price as well.)  It was so
>> nice to see the drive come to life!
>>
>> Best wishes,
>> Anthony
>>
>>
>> All on the list:  any tips on reliably using the bar code reader?  Thanks.
>> I?m threatening to inventory our pantry if I can get it working, though my
>> wife doesn?t think that?s such a practical application...  :)
>>
>> 
>>
>>
>>

Re: [M100] Bar code reader with REX / M100 Digest, Vol 87, Issue 2

[Anthony Coghlan]

Thanks, Peter. I think I’m going to try the barcode reader you use if I can
get it on eBay cheaply, as it may be more reliable anyway.  Perhaps I have
to try loading the driver and program with REX temporarily disabled as an
experiment.  I suspect a conflict in memory and don’t otherwise know how to
resolve that.

Best wishes,
Anthony



On Friday, March 2, 2018, Peter Noeth <petern0...@gmail.com> wrote:

> I don't have a REX in my M102, but I have been using the BCR to do
> "pantry" and "wine cellar" inventory. Both are in the basement, so are not
> readily accessible when one wants to know what is down there. I am not
> using the Radio Shack wand, but instead am using a UniTech
> MS120-NTCB00-SG "industrial strength" wand. It is "plug-in" compatible with
> the RS wand, and has a sapphire tip that doesn't abrade the barcode labels
> and keeps dust out of the wand. It also has better "dynamic range" so has
> no problems reading low contrast barcodes or ines in color. I am using the
> sample "Simple Inventory" program (with some modifications) that came with
> the RS Barcode Reader package. I read the "database" file into Excel
> and keep a printout in the kitchen. The program works well, and barcode
> reads are quite reliable once you get used to the swiping speed needed.
>
> As to your program conflicts, problem with many of the early computers
> with "operating systems" supplied by Microsoft, is the RAM driver concept
> is limited in practical use. Microsoft intended the RAM driver facility to
> patch a ROM driver that may have bugs or add additional planned system
> expansion (like the DVI, Bar Code Reader, TDD, Option ROM, etc.). Later
> third party developers who had a product that used their own RAM driver all
> seemed to locate them in the same address in memory (top of available RAM,
> the logical place to put it). This creates memory conflicts. Especially in
> computers using the Intel 8080/8085 processors that do not support
> "relative" addressing. Without relative addressing, the user cannot move a
> driver to a different starting address in memory without recompiling it
> first, and since the user does not get a copy of the source code, he is
> usually out of luck.
>
> There were a few attempts using programs that would read the code of the
> driver and attempt to find all of the JMP and CALL instructions and patch
> them directly to a new base starting address, but it was not always
> successful, as often times the driver would contain inline data bytes that
> would confuse the conversion program. These programs usually worked on
> computers using the Z80 processors, since it did support relative
> addressing.
>
> Regards,
>
> Peter
>
> --------
>
> 
>
> Message: 14
> Date: Fri, 2 Mar 2018 00:57:07 -0500
> From: Anthony Coghlan <coghl...@gmail.com>
> To: "m...@bitchin100.com" <m...@bitchin100.com>
> Subject: Re: [M100] Bar code reader with REX
> Message-ID:
> <CANeSRQV93k+KSUfJam+A-LGikozpWwDUBcGgeT4u-uK2OgzR-A@mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Yes, that was the drive belt I used also if I recall, made by Russell
> Industries.  I can?t find my old purchase info from eBay, but it was about
> $9 at the time.  (I think Brian mentioned that price as well.)  It was so
> nice to see the drive come to life!
>
> Best wishes,
> Anthony
>
>
> All on the list:  any tips on reliably using the bar code reader?  Thanks.
> I?m threatening to inventory our pantry if I can get it working, though my
> wife doesn?t think that?s such a practical application...  :)
>
> 
>
>
>

Re: [M100] Bar code reader with REX / M100 Digest, Vol 87, Issue 2

[Peter Noeth]

I don't have a REX in my M102, but I have been using the BCR to do "pantry"
and "wine cellar" inventory. Both are in the basement, so are not readily
accessible when one wants to know what is down there. I am not using the
Radio Shack wand, but instead am using a UniTech
MS120-NTCB00-SG "industrial strength" wand. It is "plug-in" compatible with
the RS wand, and has a sapphire tip that doesn't abrade the barcode labels
and keeps dust out of the wand. It also has better "dynamic range" so has
no problems reading low contrast barcodes or ines in color. I am using the
sample "Simple Inventory" program (with some modifications) that came with
the RS Barcode Reader package. I read the "database" file into Excel
and keep a printout in the kitchen. The program works well, and barcode
reads are quite reliable once you get used to the swiping speed needed.

As to your program conflicts, problem with many of the early computers with
"operating systems" supplied by Microsoft, is the RAM driver concept is
limited in practical use. Microsoft intended the RAM driver facility to
patch a ROM driver that may have bugs or add additional planned system
expansion (like the DVI, Bar Code Reader, TDD, Option ROM, etc.). Later
third party developers who had a product that used their own RAM driver all
seemed to locate them in the same address in memory (top of available RAM,
the logical place to put it). This creates memory conflicts. Especially in
computers using the Intel 8080/8085 processors that do not support
"relative" addressing. Without relative addressing, the user cannot move a
driver to a different starting address in memory without recompiling it
first, and since the user does not get a copy of the source code, he is
usually out of luck.

There were a few attempts using programs that would read the code of the
driver and attempt to find all of the JMP and CALL instructions and patch
them directly to a new base starting address, but it was not always
successful, as often times the driver would contain inline data bytes that
would confuse the conversion program. These programs usually worked on
computers using the Z80 processors, since it did support relative
addressing.

Regards,

Peter





Message: 14
Date: Fri, 2 Mar 2018 00:57:07 -0500
From: Anthony Coghlan <coghl...@gmail.com>
To: "m...@bitchin100.com" <m...@bitchin100.com>
Subject: Re: [M100] Bar code reader with REX
Message-ID:
<canesrqv93k+ksufjam+a-lgikozpwwdubcgget4u-uk2ogz...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Yes, that was the drive belt I used also if I recall, made by Russell
Industries.  I can?t find my old purchase info from eBay, but it was about
$9 at the time.  (I think Brian mentioned that price as well.)  It was so
nice to see the drive come to life!

Best wishes,
Anthony


All on the list:  any tips on reliably using the bar code reader?  Thanks.
I?m threatening to inventory our pantry if I can get it working, though my
wife doesn?t think that?s such a practical application...  :)

Re: [M100] Bar code reader with REX

[Anthony Coghlan]

Yes, that was the drive belt I used also if I recall, made by Russell
Industries.  I can’t find my old purchase info from eBay, but it was about
$9 at the time.  (I think Brian mentioned that price as well.)  It was so
nice to see the drive come to life!

Best wishes,
Anthony


All on the list:  any tips on reliably using the bar code reader?  Thanks.
I’m threatening to inventory our pantry if I can get it working, though my
wife doesn’t think that’s such a practical application...  :)




On Friday, March 2, 2018, Fugu ME100 <b4me...@hotmail.com> wrote:

> This is the one I used.  There might be more local equivalents, I think it
> was a pretty common VCR belt in the day.
>
>
> https://www.ebay.com/itm/8-5-IC-Flat-Rubber-Replacement-
> Belt-for-VCRs-and-More-FRW8-5-NEW-/332567541128?hash=item4d6e91f588
>
> <https://www.ebay.com/itm/8-5-IC-Flat-Rubber-Replacement-Belt-for-VCRs-and-More-FRW8-5-NEW-/332567541128?hash=item4d6e91f588>
> 8.5" IC Flat Rubber Replacement Belt for VCRs and More - FRW8.5 - NEW |
> eBay
> <https://www.ebay.com/itm/8-5-IC-Flat-Rubber-Replacement-Belt-for-VCRs-and-More-FRW8-5-NEW-/332567541128?hash=item4d6e91f588>
> www.ebay.com
> Flat rubber replacement belt, for VCRs and other electronic equipment.
> Inside circumference: 8.5". | eBay!
>
>
>
>
>
> --
> *From:* M100 <m100-boun...@lists.bitchin100.com> on behalf of Scotty
> Brown <sco...@pennmail.net>
> *Sent:* Friday, March 2, 2018 04:50
> *To:* m100@lists.bitchin100.com
> *Subject:* Re: [M100] Bar code reader with REX
>
> On the TPDD2 belt replacement - did you order something specific (that I
> can then also order :) ) ?
>
> Cheers,
>
> Scotty
>
>
> On 2/03/2018 14:33, Anthony Coghlan wrote:
> > Recently discovered that a few gadgets in my “collection” work well or
> > could work with a little effort, and I have been having fun with
> > those:  an old Apple ImageWriter (a beastly tank, but great through
> > the serial port), a TPDD2 that I had never been able to test until I
> > replaced the totally deteriorated drive belt over the holidays, and a
> > bar code reader for which I was finally able to download the drivers
> > (thanks to REX with TS-DOS, and MComm).
> >
> > The bar code reader puzzles me, though.  First, does anyone have
> > experience using one with REX installed?  Is there any
> > incompatibility?  Could I be creating a memory conflict between the
> > driver and REX?  I don’t have much experience with managing machine
> > language programs on the M100, or M102 in this case.  Just seems that
> > when I try to run the bar code reader program “as is” or following the
> > instructions in the BCR manual, with REX installed, the computer hangs
> > up.  Upon restarting, I end up with TS-DOS still in memory (if I
> > recall correctly) but not REX Manager.  I’ve had very little success
> > with BCR - basically read one bar code a handful of times, but the
> > device seems to be in perfect shape.  ANY tips would be appreciated.
> > Thanks!
> >
> > Best wishes,
> > Anthony
> >
> >
>
>

Re: [M100] Bar code reader with REX

[Scotty Brown]

Thanks!


On 2/03/2018 15:05, Fugu ME100 wrote:
>
> This is the one I used.  There might be more local equivalents, I
> think it was a pretty common VCR belt in the day.
>
>
> https://www.ebay.com/itm/8-5-IC-Flat-Rubber-Replacement-Belt-for-VCRs-and-More-FRW8-5-NEW-/332567541128?hash=item4d6e91f588
>
> <https://www.ebay.com/itm/8-5-IC-Flat-Rubber-Replacement-Belt-for-VCRs-and-More-FRW8-5-NEW-/332567541128?hash=item4d6e91f588>
>   
> 8.5" IC Flat Rubber Replacement Belt for VCRs and More - FRW8.5 - NEW
> | eBay
> <https://www.ebay.com/itm/8-5-IC-Flat-Rubber-Replacement-Belt-for-VCRs-and-More-FRW8-5-NEW-/332567541128?hash=item4d6e91f588>
> www.ebay.com
> Flat rubber replacement belt, for VCRs and other electronic equipment.
> Inside circumference: 8.5". | eBay!
>
>
>
>
>
> 
> *From:* M100 <m100-boun...@lists.bitchin100.com> on behalf of Scotty
> Brown <sco...@pennmail.net>
> *Sent:* Friday, March 2, 2018 04:50
> *To:* m100@lists.bitchin100.com
> *Subject:* Re: [M100] Bar code reader with REX
>  
> On the TPDD2 belt replacement - did you order something specific (that I
> can then also order :) ) ?
>
> Cheers,
>
> Scotty
>
>
> On 2/03/2018 14:33, Anthony Coghlan wrote:
> > Recently discovered that a few gadgets in my “collection” work well or
> > could work with a little effort, and I have been having fun with
> > those:  an old Apple ImageWriter (a beastly tank, but great through
> > the serial port), a TPDD2 that I had never been able to test until I
> > replaced the totally deteriorated drive belt over the holidays, and a
> > bar code reader for which I was finally able to download the drivers
> > (thanks to REX with TS-DOS, and MComm).  
> >
> > The bar code reader puzzles me, though.  First, does anyone have
> > experience using one with REX installed?  Is there any
> > incompatibility?  Could I be creating a memory conflict between the
> > driver and REX?  I don’t have much experience with managing machine
> > language programs on the M100, or M102 in this case.  Just seems that
> > when I try to run the bar code reader program “as is” or following the
> > instructions in the BCR manual, with REX installed, the computer hangs
> > up.  Upon restarting, I end up with TS-DOS still in memory (if I
> > recall correctly) but not REX Manager.  I’ve had very little success
> > with BCR - basically read one bar code a handful of times, but the
> > device seems to be in perfect shape.  ANY tips would be appreciated. 
> > Thanks!
> >
> > Best wishes,
> > Anthony
> >
> >
>

Re: [M100] Bar code reader with REX

[Scotty Brown]

As usual - thanks Brian!


On 2/03/2018 14:52, Brian White wrote:
> google or ebay search "FRW-8.5 belt"
>
> Pay about $9 or less, or keep looking.
>
> On Mar 1, 2018 11:50 PM, "Scotty Brown"  > wrote:
>
> On the TPDD2 belt replacement - did you order something specific
> (that I
> can then also order :) ) ?
>
> Cheers,
>
> Scotty
>
>
> On 2/03/2018 14:33, Anthony Coghlan wrote:
> > Recently discovered that a few gadgets in my “collection” work
> well or
> > could work with a little effort, and I have been having fun with
> > those:  an old Apple ImageWriter (a beastly tank, but great through
> > the serial port), a TPDD2 that I had never been able to test until I
> > replaced the totally deteriorated drive belt over the holidays,
> and a
> > bar code reader for which I was finally able to download the drivers
> > (thanks to REX with TS-DOS, and MComm).  
> >
> > The bar code reader puzzles me, though.  First, does anyone have
> > experience using one with REX installed?  Is there any
> > incompatibility?  Could I be creating a memory conflict between the
> > driver and REX?  I don’t have much experience with managing machine
> > language programs on the M100, or M102 in this case.  Just seems
> that
> > when I try to run the bar code reader program “as is” or
> following the
> > instructions in the BCR manual, with REX installed, the computer
> hangs
> > up.  Upon restarting, I end up with TS-DOS still in memory (if I
> > recall correctly) but not REX Manager.  I’ve had very little success
> > with BCR - basically read one bar code a handful of times, but the
> > device seems to be in perfect shape.  ANY tips would be
> appreciated. 
> > Thanks!
> >
> > Best wishes,
> > Anthony
> >
> >
>

Re: [M100] Bar code reader with REX

[Brian White]

google or ebay search "FRW-8.5 belt"

Pay about $9 or less, or keep looking.

On Mar 1, 2018 11:50 PM, "Scotty Brown"  wrote:

> On the TPDD2 belt replacement - did you order something specific (that I
> can then also order :) ) ?
>
> Cheers,
>
> Scotty
>
>
> On 2/03/2018 14:33, Anthony Coghlan wrote:
> > Recently discovered that a few gadgets in my “collection” work well or
> > could work with a little effort, and I have been having fun with
> > those:  an old Apple ImageWriter (a beastly tank, but great through
> > the serial port), a TPDD2 that I had never been able to test until I
> > replaced the totally deteriorated drive belt over the holidays, and a
> > bar code reader for which I was finally able to download the drivers
> > (thanks to REX with TS-DOS, and MComm).
> >
> > The bar code reader puzzles me, though.  First, does anyone have
> > experience using one with REX installed?  Is there any
> > incompatibility?  Could I be creating a memory conflict between the
> > driver and REX?  I don’t have much experience with managing machine
> > language programs on the M100, or M102 in this case.  Just seems that
> > when I try to run the bar code reader program “as is” or following the
> > instructions in the BCR manual, with REX installed, the computer hangs
> > up.  Upon restarting, I end up with TS-DOS still in memory (if I
> > recall correctly) but not REX Manager.  I’ve had very little success
> > with BCR - basically read one bar code a handful of times, but the
> > device seems to be in perfect shape.  ANY tips would be appreciated.
> > Thanks!
> >
> > Best wishes,
> > Anthony
> >
> >
>
>

Re: [M100] Bar code reader with REX

[Scotty Brown]

On the TPDD2 belt replacement - did you order something specific (that I
can then also order :) ) ?

Cheers,

Scotty


On 2/03/2018 14:33, Anthony Coghlan wrote:
> Recently discovered that a few gadgets in my “collection” work well or
> could work with a little effort, and I have been having fun with
> those:  an old Apple ImageWriter (a beastly tank, but great through
> the serial port), a TPDD2 that I had never been able to test until I
> replaced the totally deteriorated drive belt over the holidays, and a
> bar code reader for which I was finally able to download the drivers
> (thanks to REX with TS-DOS, and MComm).  
>
> The bar code reader puzzles me, though.  First, does anyone have
> experience using one with REX installed?  Is there any
> incompatibility?  Could I be creating a memory conflict between the
> driver and REX?  I don’t have much experience with managing machine
> language programs on the M100, or M102 in this case.  Just seems that
> when I try to run the bar code reader program “as is” or following the
> instructions in the BCR manual, with REX installed, the computer hangs
> up.  Upon restarting, I end up with TS-DOS still in memory (if I
> recall correctly) but not REX Manager.  I’ve had very little success
> with BCR - basically read one bar code a handful of times, but the
> device seems to be in perfect shape.  ANY tips would be appreciated. 
> Thanks!
>
> Best wishes,
> Anthony
>
>

[M100] Bar code reader with REX

[Anthony Coghlan]

Recently discovered that a few gadgets in my “collection” work well or
could work with a little effort, and I have been having fun with those:  an
old Apple ImageWriter (a beastly tank, but great through the serial port),
a TPDD2 that I had never been able to test until I replaced the totally
deteriorated drive belt over the holidays, and a bar code reader for which
I was finally able to download the drivers (thanks to REX with TS-DOS, and
MComm).

The bar code reader puzzles me, though.  First, does anyone have experience
using one with REX installed?  Is there any incompatibility?  Could I be
creating a memory conflict between the driver and REX?  I don’t have much
experience with managing machine language programs on the M100, or M102 in
this case.  Just seems that when I try to run the bar code reader program
“as is” or following the instructions in the BCR manual, with REX
installed, the computer hangs up.  Upon restarting, I end up with TS-DOS
still in memory (if I recall correctly) but not REX Manager.  I’ve had very
little success with BCR - basically read one bar code a handful of times,
but the device seems to be in perfect shape.  ANY tips would be
appreciated.  Thanks!

Best wishes,
Anthony