I-Appliance BBS
The Official Source for Internet Appliance Upgrades and Mods
Amazon Honor System Click Here to Pay Learn More
BBS Main List | Sign In | Sign Up | Search | Help | Linux-Hacker.netReply to Thread | Printer |

Home / I-Appliance BBS General / NEWS, Breaking NEWS
WARNING: NPLI updated my virgin i-o via my own ISP - following Just-Do-Its instructions

New MessageWARNING: NPLI updated my virgin i-o via my own ISP - following Just-Do-Its instructions (modified 0 times) piz'ed
Well I followed "Just_Do_Its" instructions, as well as had several other similar ones to hand. My i-opener was a virgin - it ain't now.

I followed all of the dsmod commands, double checking each one and checking the response was correct.

Killed the two update processes (one mentioned Phoenix, can't remember the other). Plugged the phone in - nothing.

Rebooted the i-opener. Got the shell, checked any update processes: none. Connected the phone line.

It dialed out, and I did a ifconfig ppp0 to check it was connecting to my ISP. Logged into the ftp site and was just about to grab the needed files when, in the main screen, the one behind the small # prompt window I see the ominous words "Update Complete."

This means that even though I used my own ISP, changed the loginhost0 and 1 AND checked no update PIDs were running, Netpliance was still able, and did update my I-Opener.

I'm furious! Did something change between yesterday and today? How come nobody else has mentioned this?

Now what the ###k am I supposed to do?

Whenever I reboot the i-opener - without the phone plugged in - I can only hold a shell window for about 10 seconds and then it goes directly into the i-opener screen (mail, news and other crap) and kicks me out of the shell. I've tried doing a kill -9 * while in the shell (before getting booted out) hoping that this might kill the i-opener screen crap. That didn't work.

Can anyone give me any advice as to what to do now? I really don't want to shell out big bucks to get a new BIOS. Plus I was up till 2am this morning getting my 9.5 mm hard drive set up. This is a MAJOR bummer to me.

Is there some way of preventing the i-opener screen from running, giving me more time in the shell so that I can try the procedure again?

04-22-2000 16:03:41

New MessageRE:WARNING: NPLI updated my virgin i-o via my own ISP - following Just-Do-Its instructions (modified 0 times) DoctorJ
Don't start a panic! I saw the same "Update Complete." message when I finally connected to my ISP and downloaded the old BIOS/qnxflash... but I don't really think the "Update" did anything at all.

My IO out of the box only gave me 10 seconds in the shell window! I never ran the tutorial for more than the 10 seconds required to defeat it, and hadn't plugged in the phone line.

But, that 10 seconds is enough to vi /etc/passwd, delete the 'x' from the root password entry, save, quit, and execute /app/stop-apps. That kills the Netpliance apps. Then create a /app/ztest/startup script so when you restart it won't continue to run the rest of the IO software.

Do some more reading before you attempt to alarm the rest of the world. From what you've posted, it doesn't sound like there is any problem... hence why no one else has posted.

04-22-2000 18:57:43

New MessageRE:WARNING: NPLI updated my virgin i-o via my own ISP - following Just-Do-Its instructions (modified 0 times) just_did_it
i noticed that it was saying update complete also. but, it didn't actually update anything. I proceeded with the directions and when i rebooted the bios was dated 10/01/1999 or something like that! orginally it was 03/23/2000.

If I were you I would try again. Heck it couldn't hurt anything!

04-22-2000 21:48:26

New MessageRE:WARNING: NPLI updated my virgin i-o via my own ISP - following Just-Do-Its instructions (modified 0 times) piz'ed
Yes, sorry everyone - no need to panic: at least not yet. There's a few things going on here and I don't have the technical expertise to decipher it all. I'm certain that the update PIDs were not running when I rebooted my io to run the new nvram and called my own ISP. I did the ifconfig to confirm my ISP's IP was showing. However, soon afterwards, the update PIDs did kick in. Netpiiance "wrote" to my box. They uploaded some mail, news and other general crap. More sinister though, I'd backed up /app/ztest/nvram.bak to /dev/hd0t98. I tried to restore it after the update (and after rebooting) and this file had been removed.

We know Netpliance reads this board. Things we warn each other about get picked up. NPLI probobly will try to kill ftp and qtalk on the box if given a chance. The qnxflash has only been out for a few days and many, many people have had great success with it. However NPLI must be trying to put a stop to it any way they can. If the box calls home, they have that opportunity.

DoctorJ, you mentioned creating a /app/ztest/startup script. This sounds like a great idea. Would you have the time to give me a few pointer on how to do this (I'm not vi-savvy and I'd have to research what the chmod should be to make the script runable). Does anyone have a few minutes to develop such a script, with comments about how to implement, and then post it on a ftp site?

It would be great to be able to use the i-opener, SAFELY until I get the hard drive set up. If the box NEVER called home, it would be a nice little box to use without any hard drive (if I could figure out how to bring up voyager from the prompt!)

So sorry, wrists slapped, but the warning is a somewhat valid one. You folks be careful out there!

04-22-2000 23:29:50

Reply to Thread | Printer |
All times are PSTPowered by UltraBoard v1.62



Copyright © 2000, Netmake Inc. All Rights Reserved.
See Terms and Conditions for more information.




i-opener opener laptop notebook computer help drivers dll free windows dos repair fix linux mac macintosh 2000 95 98 nt pc configure hardware software sound video netscape explorer network networking lan wan software cmos fat bios printer card mouse modem ide scsi cd rom controllers scanner tape hard drive cgi scripts source code mp3