PRC as a amplifier in GPS question.

On 9/08/2014 8:18 PM, BuckyBalls wrote:
On 8/08/2014 4:08 PM, Clocky wrote:
On 8/08/2014 9:22 PM, BuckyBalls wrote:
On 8/08/2014 1:06 PM, Cl

Probably was but when I was given the scanner by a friend who was going
to send it for recycling and it didn't come with any software or drivers.
I didn't have much hope for getting it to work with Windows 7 but it
turns out that it's perfectly fit for my particular needs.


So what software do you use with it? (Or works with it!)
Expect a reply laced with gibberish as per usual
( simeon based of course)

--









X-No-Archive: Yes
 
On 10/08/2014 9:47 AM, Jeßus wrote:
On Sun, 10 Aug 2014 07:19:27 +1000, atec77 <"atec77 "@hotmail.com
wrote:

On 9/08/2014 8:18 PM, BuckyBalls wrote:
On 8/08/2014 4:08 PM, Clocky wrote:
On 8/08/2014 9:22 PM, BuckyBalls wrote:
On 8/08/2014 1:06 PM, Cl

Probably was but when I was given the scanner by a friend who was going
to send it for recycling and it didn't come with any software or drivers.
I didn't have much hope for getting it to work with Windows 7 but it
turns out that it's perfectly fit for my particular needs.


So what software do you use with it? (Or works with it!)

Expect a reply laced with gibberish as per usual
( simeon based of course)

I'm sending this post off to dictionary.com, and will suggest this as
the updated description for irony.

LOL, his brainstem fired again and produced all it is capable of.

Anyway, I'm using the default scanner software that Windows 7 uses
whenever you install a driver. Basically the scanner appears in "Devices
and Printers", you right click on it and select scan.

BTW the other software mentioned works very well too if your scanner
doesn't have a driver (or a crappy one).

Downloadable as a demo or from the usual places if you want to try the
full version before purchasing.
 
On Sun, 10 Aug 2014 07:19:27 +1000, atec77 <"atec77 "@hotmail.com>
wrote:

On 9/08/2014 8:18 PM, BuckyBalls wrote:
On 8/08/2014 4:08 PM, Clocky wrote:
On 8/08/2014 9:22 PM, BuckyBalls wrote:
On 8/08/2014 1:06 PM, Cl

Probably was but when I was given the scanner by a friend who was going
to send it for recycling and it didn't come with any software or drivers.
I didn't have much hope for getting it to work with Windows 7 but it
turns out that it's perfectly fit for my particular needs.


So what software do you use with it? (Or works with it!)

Expect a reply laced with gibberish as per usual
( simeon based of course)

I'm sending this post off to dictionary.com, and will suggest this as
the updated description for irony.
 
On Sun, 10 Aug 2014 10:55:09 +0800, Clocky <notgonn@happen.com> wrote:

On 10/08/2014 9:47 AM, Jeßus wrote:
On Sun, 10 Aug 2014 07:19:27 +1000, atec77 <"atec77 "@hotmail.com
wrote:

On 9/08/2014 8:18 PM, BuckyBalls wrote:
On 8/08/2014 4:08 PM, Clocky wrote:
On 8/08/2014 9:22 PM, BuckyBalls wrote:
On 8/08/2014 1:06 PM, Cl

Probably was but when I was given the scanner by a friend who was going
to send it for recycling and it didn't come with any software or drivers.
I didn't have much hope for getting it to work with Windows 7 but it
turns out that it's perfectly fit for my particular needs.


So what software do you use with it? (Or works with it!)

Expect a reply laced with gibberish as per usual
( simeon based of course)

I'm sending this post off to dictionary.com, and will suggest this as
the updated description for irony.


LOL, his brainstem fired again and produced all it is capable of.

He must've been having a particularly good day, that day... it's just
about the most erudite and legible thing ever to come from Atec.
 
On 11/08/2014 3:32 PM, Jeßus wrote:
On Sun, 10 Aug 2014 10:55:09 +0800, Clocky <notgonn@happen.com> wrote:

On 10/08/2014 9:47 AM, Jeßus wrote:
On Sun, 10 Aug 2014 07:19:27 +1000, atec77 <"atec77 "@hotmail.com
wrote:

On 9/08/2014 8:18 PM, BuckyBalls wrote:
On 8/08/2014 4:08 PM, Clocky wrote:
On 8/08/2014 9:22 PM, BuckyBalls wrote:
On 8/08/2014 1:06 PM, Cl

Probably was but when I was given the scanner by a friend who was going
to send it for recycling and it didn't come with any software or drivers.
I didn't have much hope for getting it to work with Windows 7 but it
turns out that it's perfectly fit for my particular needs.


So what software do you use with it? (Or works with it!)

Expect a reply laced with gibberish as per usual
( simeon based of course)

I'm sending this post off to dictionary.com, and will suggest this as
the updated description for irony.


LOL, his brainstem fired again and produced all it is capable of.

He must've been having a particularly good day, that day... it's just
about the most erudite and legible thing ever to come from Atec.

Seems even his train-wreck of a mind has occasional lucid moments, well
in terms of literacy in any case.

The content of his posts still just amounts to white noise produced by a
retarded and imbecilic mind incapable of reasoned and rational thought,
however.
 
On Tue, 26 Aug 2014 09:30:44 +1000, Jonz <mpajero@4WD.again.com>
wrote:

which Aus.cars member this is?:

https://www.youtube.com/watch?v=RsX9HdP_zUs

Dunno, but the name Rod Speed came to mind instantly.
Or maybe Phalluson...
 
On 28/08/2014 10:18 AM, Jeßus wrote:
On Tue, 26 Aug 2014 09:30:44 +1000, Jonz <mpajero@4WD.again.com
wrote:

which Aus.cars member this is?:

https://www.youtube.com/watch?v=RsX9HdP_zUs

Dunno, but the name Rod Speed came to mind instantly.
Or maybe Phalluson...

I could see it being Filthy, but he lives in Sydney.
 
On Thu, 28 Aug 2014 16:28:32 +1000, keithr <user@domain.invalid>
wrote:

On 28/08/2014 10:18 AM, Jeßus wrote:
On Tue, 26 Aug 2014 09:30:44 +1000, Jonz <mpajero@4WD.again.com
wrote:

which Aus.cars member this is?:

https://www.youtube.com/watch?v=RsX9HdP_zUs

Dunno, but the name Rod Speed came to mind instantly.
Or maybe Phalluson...

I could see it being Filthy, but he lives in Sydney.

Hmm, true.
 
On Sat, 25 Oct 2014 12:14:27 +0800, Shed_Fiddler <asdf@hjkl.com.au> wrote:

Lifted from another NG:



Hi,

I know there are several people here that work with Arduino
microcontrollers. Just a heads up to a potential headache.

===
Windows Update drivers bricking USB serial chips beloved of hardware
hackers The move to combat counterfeit chips leaves hobbyists stuck in
the middle.

by Peter Bright - Oct 23, 2014 12:40 am UTC

Hardware hackers building interactive gadgets based on the Arduino
microcontrollers are finding that a recent driver update that Microsoft
deployed over Windows Update has bricked some of their hardware,
leaving it inaccessible to most software both on Windows and Linux.
This came to us via hardware hacking site Hack A Day...
===

See:

http://arstechnica.com/information-technology/2014/10/windows-update-drivers-bricking-usb-serial-chips-beloved-of-hardware-hackers/

You're behind the times already, MS pulled the drivers Friday.

Grant.
 
On 10/27/2014 3:52 PM, WangoTango wrote:
In article <fP-dnRLRcvMIvtbJnZ2dnUU7-VudnZ2d@westnet.com.au>,
asdf@hjkl.com.au says...
Lifted from another NG:



Hi,

I know there are several people here that work with Arduino
microcontrollers. Just a heads up to a potential headache.

===
Windows Update drivers bricking USB serial chips beloved of hardware
hackers The move to combat counterfeit chips leaves hobbyists stuck in
the middle.

by Peter Bright - Oct 23, 2014 12:40 am UTC

Hardware hackers building interactive gadgets based on the Arduino
microcontrollers are finding that a recent driver update that Microsoft
deployed over Windows Update has bricked some of their hardware,
leaving it inaccessible to most software both on Windows and Linux.
This came to us via hardware hacking site Hack A Day...
===

See:

http://arstechnica.com/information-technology/2014/10/windows-update-drivers-bricking-usb-serial-chips-beloved-of-hardware-hackers/


What I usually find is that when you steal a VID and PID you might need
to expect such things.

I have seen commercial products that use Microchip's VID and use the PID
from their USB->Serial development kit. Why should people be surprised
when that product gets bricked?

I'll bet most didn't know it wasn't an FTDI based product and only
learned when it stopped working. A driver that doesn't work with the
fake hardware is one thing. A driver that makes the hardware not work
with *any* driver is a different matter.


Does USB.org make being a USB hobbyist easy, shit no, but most IC
companies will give you a PID if you fill out their request form, and if
you are putting items out in the wild with snagged VID/PID pairs, well,
for shame.

It's not the product maker who suffers harm in this case, it is the user
harmed not once but twice.

--

Rick
 
On 28/10/2014 6:52 AM, WangoTango wrote:
In article <fP-dnRLRcvMIvtbJnZ2dnUU7-VudnZ2d@westnet.com.au>,
asdf@hjkl.com.au says...
Lifted from another NG:



Hi,

I know there are several people here that work with Arduino
microcontrollers. Just a heads up to a potential headache.

===
Windows Update drivers bricking USB serial chips beloved of hardware
hackers The move to combat counterfeit chips leaves hobbyists stuck in
the middle.

by Peter Bright - Oct 23, 2014 12:40 am UTC

Hardware hackers building interactive gadgets based on the Arduino
microcontrollers are finding that a recent driver update that Microsoft
deployed over Windows Update has bricked some of their hardware,
leaving it inaccessible to most software both on Windows and Linux.
This came to us via hardware hacking site Hack A Day...
===

See:

http://arstechnica.com/information-technology/2014/10/windows-update-drivers-bricking-usb-serial-chips-beloved-of-hardware-hackers/


What I usually find is that when you steal a VID and PID you might need
to expect such things.

Not really. The worst you'd expect is that it might not work. You don't
expect someone to go out of their way to find a way of bricking your device.

Sylvia.
 
On 28-Oct-14 12:00 PM, Sylvia Else wrote:

What I usually find is that when you steal a VID and PID you might need
to expect such things.

Not really. The worst you'd expect is that it might not work. You don't expect someone to go out of their way to find a
way of bricking your device.

Sylvia.

should have simply displayed a message that the updated software doesn't support the device, as it isn't an FTDI product.

Cheers Don...



--
Don McKenzie

http://www.dontronics-shop.com

All Olimex products now 50% to 95% off normal Olimex Prices.
http://www.dontronics-shop.com/olimex-ltd.html
Many other items discounted up to 90% off.
Also discounts on FTDI, Sparkfun, mELABS, CCS, SimmStick, etc.
 
On 2014-10-28, rickman <gnuarm@gmail.com> wrote:
On 10/27/2014 5:34 AM, John Devereux wrote:
Jasen Betts <jasen@xnet.co.nz> writes:

So, what do you do? go with prolific's PL230x parts and hope the don't
"update" their drivers again, or go with SiLabs CP2101 because they
haven't pulled a similar stunt (yet), or roll your own?

Indeed, that is the question. I was not aware of problems with the
prolific stuff until I read this thread; we use those too. Although
tracking down the correct drivers always seemed a bit harder.

I haven't seen anything indicating Prolific has a problem with their
drivers. Where was that posted? I'm not counting the above statement.

eg: http://www.eevblog.com/forum/reviews/note-how-to-not-get-scammed-with-prolific-%28pl2303%29-usb-serial-adapters/

Really we use them out of lazyness (or a cost-benefit analysis of our
time if you prefer). These days all the microcontrollers have USB
hardware. So I suppose we should roll our own.

There is a $4 eval board from TI with an ARM CM3 on it (or is it a CM4).
It also has another chip which is the same sort of USB to UART which
can be broken off of the rest of the board and used separately.

Their "MSP430 launchpad" eval board has that too, the serial
inerface quits after about 10 minutes abd needs to be "re-plugged". Dunno if this
is intentional or a bug.

--
umop apisdn
 
On Fri, 31 Oct 2014 15:33:22 +1100, Sylvia Else
<sylvia@not.at.this.address> wrote:

On 31/10/2014 2:08 PM, josephkk wrote:
On Thu, 30 Oct 2014 15:12:42 +1100, Sylvia Else
sylvia@not.at.this.address> wrote:

On 30/10/2014 6:24 AM, WangoTango wrote:
In article <cbb8igFhgolU1@mid.individual.net>,
sylvia@not.at.this.address says...
It's worth remembering that there's nothing unlawful about reverse
engineering an interface, and implementing a chip that supports it, and
that's what the 'fake' FTDI chip makers have done.

It is worth noting that stealing their VID and PID is bullshit.

How is it possible to steal a VID and PID?

They're just numbers. No one owns them.

Sylvia.

The numbers themselves not own able. Their use in specific licensed,
trademarked, specific application domain "USB PID and VID" is a wholly
different matter. That use is controlled and licensed by the USB
consortium.

?-)


If there were a law that allowed the USB consortium to control the use
of PIDs in the context of USB, then misuse would be against the law. But
there is no such law.

That _is_ covered by trademark law and contract law. It is breach of
contract or fraud to violate the terms of the licence to misuse the
numbers in the context of USB.
There may have been a violation of the USB trademark, but we don't know
that, in any particular instance, and neither does FTDI. In any case,
there's no law that allows a trademark holder to make a unilateral
decison to destroy trademark violating goods.

That is correct. FTDI blew it on this one.

?-)
 
On 1/11/2014 2:30 PM, josephkk wrote:
On Fri, 31 Oct 2014 15:33:22 +1100, Sylvia Else
sylvia@not.at.this.address> wrote:

On 31/10/2014 2:08 PM, josephkk wrote:
On Thu, 30 Oct 2014 15:12:42 +1100, Sylvia Else
sylvia@not.at.this.address> wrote:

On 30/10/2014 6:24 AM, WangoTango wrote:
In article <cbb8igFhgolU1@mid.individual.net>,
sylvia@not.at.this.address says...
It's worth remembering that there's nothing unlawful about
reverse engineering an interface, and implementing a chip
that supports it, and that's what the 'fake' FTDI chip
makers have done.

It is worth noting that stealing their VID and PID is
bullshit.

How is it possible to steal a VID and PID?

They're just numbers. No one owns them.

Sylvia.

The numbers themselves not own able. Their use in specific
licensed, trademarked, specific application domain "USB PID and
VID" is a wholly different matter. That use is controlled and
licensed by the USB consortium.

?-)


If there were a law that allowed the USB consortium to control the
use of PIDs in the context of USB, then misuse would be against the
law. But there is no such law.

That _is_ covered by trademark law and contract law. It is breach
of contract or fraud to violate the terms of the licence to misuse
the numbers in the context of USB.

The manufacturers of the clones don't have a licence agreement with the
USB consortium, so they cannot be violating the terms of it. Similarly,
there's no contract.

The USB logos are trademarked, but we don't know that they are being
used on the clones. As far as I can see, there has been no attempt to
trademark the abbreviation USB.


Sylvia.
 
On Friday, 29 March 1996 19:00:00 UTC+11, John Miller wrote:
(Matthew Josh) wrote:

I have access to an old BWD oscilloscope but it has a worn out
tube.... and the BWD company seems to have go out of business


I was wondering if anyone knew where to find a replacement tube...


Mail me on

I'm replying by this mode rather than e-mail, Matthew, so that others
may know what has happened to BWD, and because for some reason all my
mail for the last 12 months is still on the e-mail server, exceeding
my quota of disc space and I can't find out how to kill it!.

About 6 and a bit years ago BWD went into receivership and the assets
were bought by Bob McPherson and John van de Vreede, who re-named the
firm (because they had to legally) McVan Instruments. We are basically
the same people on the technical side, service, production etc.

The phone number is (03) 9561 2888 ext 38 for the service/spares
department

Fax (03) 9560 1164

Depending on how old the scope is we _may_ still have spares as we try
to provide full support up to ten years, and whatever we can after
that.

Cheers
,-._|\ John Miller
/ Oz \ jayem@melbpc.org.au Member of Melbourne PC User Group.
\_,--.x/ Packet radio: VK3DJM@VK3KSD.#MEL.VIC.AUS.OC
v

Hi John,
I know this is a very thread but I'm getting to the end of my search.
I have found an old BWD 430 Oscilloscope that currently doesn't work.
I have been unable so far to find any info at all on this unit and would dearly like
to bring it back to life if possible. I'm an old sparky and am doing some electronics courses online so I can maybe work on old analog audio gear.
I was hoping that you might have some info on this old scope or maybe
even a manual or schematic :)
thanks in advance Phil Murray
 
phil...@gmail.com wrote:

Hi John,
I know this is a very thread but I'm getting to the end of my search.

** Replying to an almost 20 year old thread is an act of insanity.



I have found an old BWD 430 Oscilloscope that currently doesn't work.

** Really - how amazing.

I am a long time BWD scope owner ( 804, 824 and 825 ) and fan but that number rings no bells.

Post a pic of it somewhere with a link.

Its' not a 1960s valve model is it ?




.... Phil
 
Phil Allison wrote:


I am a long time BWD scope owner ( 804, 824 and 825 ) and fan but that number rings no bells.

Post a pic of it somewhere with a link.

Its' not a 1960s valve model is it ?

** You posted a link to a pic of the BWD430 on the EEV blog forum - so why not here too ?

Its looks like an early 1970s hybrid (valve/SS) model.

Obscure as all hell.

FYI:

I reckon I'm damn lucky to still keep my mid 1980s BWDs working - and I went out of my way to buy crucial spares ( like a Matsushita 140 CGB31 internal graticule, mesh PDA CRT and some Natsemi NPD8303 8pin, DIL dual fets )long in advance of them becoming completely unobtainable.

What did you do ?



.... Phil
 
On 27/11/2014 9:57 PM, Phil Allison wrote:
Phil Allison wrote:


I am a long time BWD scope owner ( 804, 824 and 825 ) and fan but that number rings no bells.

Post a pic of it somewhere with a link.

Its' not a 1960s valve model is it ?


** You posted a link to a pic of the BWD430 on the EEV blog forum - so why not here too ?

Its looks like an early 1970s hybrid (valve/SS) model.

Obscure as all hell.

FYI:

I reckon I'm damn lucky to still keep my mid 1980s BWDs working - and I went out of my way to buy crucial spares ( like a Matsushita 140 CGB31 internal graticule, mesh PDA CRT and some Natsemi NPD8303 8pin, DIL dual fets )long in advance of them becoming completely unobtainable.

What did you do ?



... Phil
I know its fun to play with old gear, but realistically, you can buy
something like a modern Rigol scope for around $400 or so, and it will
work perfectly for troubleshooting on old audio circuits, and much else
besides.

While you might get a replacement tube to work, what about all those
dried out electrolytic caps in the power supply ? To say nothing of the
carbon composition resistors, which will have changed value
significantly, wrecking any calibration, at the very best.

Those ancient BWD scopes were never very good, and cost in 1970s dollars
about the same as a modern one in 2014 dollars.

I guess the question is whether you want a tool or a project.

--
Regards,

Adrian Jansen adrianjansen at internode dot on dot net
Note reply address is invalid, convert address above to machine form.
 
On 28/11/2014 12:17 PM, Adrian Jansen wrote:
On 27/11/2014 9:57 PM, Phil Allison wrote:
Phil Allison wrote:


I am a long time BWD scope owner ( 804, 824 and 825 ) and fan but
that number rings no bells.

Post a pic of it somewhere with a link.

Its' not a 1960s valve model is it ?


** You posted a link to a pic of the BWD430 on the EEV blog forum - so
why not here too ?

Its looks like an early 1970s hybrid (valve/SS) model.

Obscure as all hell.

FYI:

I reckon I'm damn lucky to still keep my mid 1980s BWDs working - and
I went out of my way to buy crucial spares ( like a Matsushita 140
CGB31 internal graticule, mesh PDA CRT and some Natsemi NPD8303 8pin,
DIL dual fets )long in advance of them becoming completely unobtainable.

What did you do ?



... Phil







I know its fun to play with old gear, but realistically, you can buy
something like a modern Rigol scope for around $400 or so, and it will
work perfectly for troubleshooting on old audio circuits, and much else
besides.

While you might get a replacement tube to work, what about all those
dried out electrolytic caps in the power supply ? To say nothing of the
carbon composition resistors, which will have changed value
significantly, wrecking any calibration, at the very best.

Those ancient BWD scopes were never very good, and cost in 1970s dollars
about the same as a modern one in 2014 dollars.

I guess the question is whether you want a tool or a project.

You don't need much accuracy for fixing toasters.
 

Welcome to EDABoard.com

Sponsor

Back
Top