Marc
Try *# on power up, it should display 20, then do a #20 to display the
existing code, then *20 to change the installer code.
--
Crash Gordon
-------ouch------
<I feel like I'm diagonally parked in a parallel universe>
"Marc" <mlipo...@cox.net> wrote in message
news:rMEPi.304$qv6...@newsfe04.phx...
Considering the way the panel firmware is written, it's likely that
only the sub-routine for editing the dialer number has been blocked.
Thus, with a chip burner someone could easily alter the number. The
panel would then be locked onto whatever new dialer number you
assign, effectively beating Monitronics at their own sleazy game.
Hmm. Maybe Monitronics will start filing Brinks-style lawsuits. :^)
--
Regards,
Robert L Bass
=============================>
Bass Home Electronics
941-925-8650
4883 Fallcrest Circle
Sarasota · Florida · 34233
http://www.bassburglaralarms.com
=============================>
"Crash Gordon" <webm...@siriussystems.invalid> wrote in message
news:470f7c1e$0$497$815e...@news.qwest.net...
--
Crash Gordon
-------ouch------
<I feel like I'm diagonally parked in a parallel universe>
"Roland Moore" <nos...@nospam.com> wrote in message
news:470f85a6$0$24352$4c36...@roadrunner.com...
M
You should be able to get into programming. But if you cannot remove the
dialer # and account number the panel will alway try to dial when it has
something to send, and since you will unplug it from the telco line...it
will fail to communicate. This will display FC on the keypad - everyday if
they have it set to test daily (I doubt it) but when ever you want to clear
the FC you may have to go into programming then exit again. This will be a
PITA.
In the long run you will end up buying a new Vista 15P :-) --- they're not
all that expensive. In fact you probably could step down to a 10P -
depending on what all is in the system.
--
Crash Gordon
-------ouch------
<I feel like I'm diagonally parked in a parallel universe>
"Marc" <mlipo...@cox.net> wrote in message
news:Hc_Pi.462$qv6...@newsfe04.phx...
Jim Rojas
"Jim Rojas" <jrojas+tech-man.com> wrote in message
news:4710d94b$0$25721$4c36...@roadrunner.com...
Jim Rojas
"Jim Rojas" <jrojas+tech-man.com> wrote in message
news:4710fc33$0$5010$4c36...@roadrunner.com...
Only problem with that is by default they do have phone numbers in fields 41
and 42
First of all, he's not giving up any "trade secrets". He's obviously
had some experience with Ademco (Honeywell) products and understands how
they're manufactured and what makes them "tick". I don't know Jim all
that well, but I understand that his whole house is a warehouse of used
parts (which would make the Federal Marshal's job all that more
difficult to find the computers buried under all that junk). Which
reminds me... Have the Federal Marshals visited the Rojas household and
place of business? It seems the "Emergency Order" Brinks wanted carried
a "double whammy". They wanted the website shut down (which I
understand they didn't succeed at because Jim's provider couldn't find
any Brinks intellectual property in it), and they wanted Jim's computers.
Since Brinks request for an "Emergency Order" (the part where they
demanded the court order www.tech-man.com shut down was based on false
information provided by Brinks Attorneys), and the revelation from Jim
this morning that his provider could find nothing belonging to Brinks in
any of the files on their server, it makes me wonder if this whole thing
might "cave in" on October 26th (when Jim's been ordered to appear in
Texas Federal Court). I might suggest that Jim obtain a letter from his
provider with suitable language to the effect that there wasn't any IP
belonging to Brinks on his website. So far the biggest culprit in all
of this is AlarmsBC's website (and I don't see any action being taken
against them).
Jim Rojas
"Jim Rojas" <jrojas+tech-man.com> wrote in message
news:47112142$0$26408$4c36...@roadrunner.com...
--
Crash Gordon
-------ouch------
<I feel like I'm diagonally parked in a parallel universe>
"Jim Rojas" <jrojas+tech-man.com> wrote in message
news:4710d94b$0$25721$4c36...@roadrunner.com...