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-Opener Areas / I-Opener Technical Stuff
That darn boot logo... A fix?
Hopefully a way to get rid of that logo or substitute your own.

New MessageThat darn boot logo... A fix? (modified 0 times) shrapnel
Yeah, I started a new thread. Even though the topic's been posted so many other times/places/contexts, I figured this deserved a new one.

I've been working on this for a good while now, but simply don't have time to verify the procedure for myself (would have to rig up a DOS HD, run it, any complications would require more time to fix, etc.), but I think I know how to change/get rid of the BIOS boot image without firing up your hex editor...

The Award BIOS used here is very modular. It can accept things like standard VGA drivers, SCSI drivers, even some network driver support. The boot logo is a module as well.

First, grab a 256K image of the BIOS. I used AWDFLASH v7.52C, but newer versions should work as well. Try "awdflash /pn iopener.bin" to just get a copy of it w/o doing any flash operations at all.

Now that you've got an image, make a copy so if you screw up, you have a backup to work with.

Grab a copy of CBROM. Mine is CBROM v1.30 which supports the logo module. I've found it in archives called CBROM130.ZIP.

When you pull up the command options for this one, there are a few of interest: /D to display modules in the BIOS w/original filenames, /logo to manipulate the logo module. Displaying modules in the image is somewhat interesting; there's the base module, an "Other" mystery module, "YGROUP ROM", "VGA ROM", and "LOGO BitMap" (which also shows an original filename of 'welcome.bmp' beside it).

You can do 3 things with each module. Extract, Release, and Add. Extract dumps the module to a file. Release removes it from the BIOS (not, however, altering the size of the BIOS file). You can also put a new module file into the image.

I used "cbrom130 iopener.bin /logo extract" to get the logo out to a file, but Paintbrush and Photoshop don't want to open it. Not sure quite why that is. Probably has something to do with the fact that it's a binary module now, not necessarily an image.

"cbrom130 iopener.bin /logo release" removes it from the list of modules you get when you use "cbrom124 iopener.bin /D". This should disable the boot logo altogether -- this would be a very good thing for those who want unattended console OS booting (like me)..

"cbrom130 iopener.bin /logo tux.bmp" causes the program to do a little "..." status thing while it compresses the bitmap for use in the BIOS. After running the command, a "/D" shows the "LOGO BitMap" module with the filename changed to your input file. This should change the boot logo.

The bitmap used must be 640x464 (that's why you see the black bar at the bottom of NetP's boot logo), 16-color. I've also read somewhere or other that Photoshop puts a spin on the file format in such a way that it doesn't like to work with BIOSen. Try The Gimp instead. Or Paintbrush or Paint Shop or something.

Last step would be to flash the BIOS with the new image ("awdflash /py iopener.bin /sy"). This is the part I haven't tried yet. Things have gotten hectic, and I won't be able to try it for some time. It would be great if someone could confirm it for me.

Finally, some good BIOS sites are www.ping.be (Wim's BIOS page) and velociraptor.mni.fh-giessen.de/Bootlogo/ (in German, use babelfish). I figured out about 75% of the process, then found I had been preceded by some work on the above sites. =) Oh well.

04-02-2000 20:37:02

New MessageRE:That darn boot logo... A fix? (modified 0 times) Tackhead
Verified! AWDFLASH 6.31 and CBROM130 here.

And I think we've just set a record for fastest mutually-independent verification of a hack that this board has ever seen!

04-02-2000 21:48:57

New MessageRE:That darn boot logo... A fix? (modified 0 times) coolbeans
http://www.geocities.com/SiliconValley/Chip/4378/

Here is a english site with the files...

Coolbeans

04-03-2000 01:57:49

New MessageRE:That darn boot logo... A fix? (modified 0 times) shrapnel
Heh, verified alright. Geez. =) Way cool.

So has anyone tried the elimination option ("release")? Or is that what you meant by "verified", Tackhead?

04-03-2000 06:05:48

New MessageRE:That darn boot logo... A fix? (modified 0 times) duvell
I tried the release option but wasn't as successful as others. My I-opener in now a door opener, well a doorstop!

I copied the flash, listed modules using cbrom and then I extracted the logo to a file. I didn't particularly want a logo so I just used the logo release option on the bios image. I wrote it back using awdflash and rebooted.

Er...tried to reboot. Repowering left me with a black screen, it didn't even turn the display on.

It is completely possible it was my user error that lead to this. I have no reason to beleive the instructions or tools were not correct. I am not sure of what versions of the tools I used, I think it was 1.24 for cbrom and 6.31 for awdflash but I am not certain.

I only post now because it was asked if anybody had tried the release option.

Now I need, to find a prom burner; I did backup the BIOS first so I do have an image. I just don't know how to program it!

Anyone in Austin have one that will accomodate the package type of the IOs flash eprom?

04-03-2000 06:34:05

New MessageRE:That darn boot logo... A fix? (modified 0 times) shrapnel
Ack, sorry about that.. I guess from here on in it should only be tested with newer software & by people with access to burners *or* experience with the similar-motherboard-hot-swap-flash trick..
04-03-2000 08:43:28

New MessageRE:That darn boot logo... A fix? (modified 0 times) Tackhead
Shrapnel: I didn't try the "/release" option to nuke the boot logo altogether. I should have, now that I think about it.

Duvell: Ouch! I hope the following will be of help, but unless you can find another i-opener and do the hot-BIOS-swap, you may have to find someone with an EPROM burner.

If you can get CBROM130, you should be able to tell whether CBROM124 or CBROM130 are producing the same BIOS image file when you /release the logo or change it to YOURFILE.BMP.

If CBROM124 and CBROM130 are producing different BIOS image files, we'll know which version not to use. If they produce the same image file, we'll know it's either the flasher or the /release option.

(I have not yet tried /release to nuke the logo altogether.)

Anyways, you may be able to reburn the BIOS by wire-wrapping a DIP-to-PLCC adapter and reading it in as a 27020 EPROM or 29020 flash ROM. If the programming software doesn't support a 39020, you may have to find a 29020. Do *not* program a 39020 as a 29020; IIRC the 29020 uses +12V to program and the key selling point of the 39020 is that it's +5V flashable. (There are probably 32-pin PLCC versions of the 27020 too, but they'll be very expensive compared to the flash version...)

If you want to flash your new chip from within the actual i-opener unit itself, you'll use the 39020, which is +5V flashable. "Fortunately", you have a "blank" 39020 sitting in your new doorstop :(

(I'd guess that a 29020 will be an OK replacement if you can't find burner/software combo for 39020. Come to think of it, if the i-opener does a BIOS update when it phones home, having a 29020 which requires +12V to program might be good protection

04-03-2000 11:26:17

New MessageRE:That darn boot logo... A fix? (modified 0 times) duvell
shrapnel & Tackhead:

I did get another prom burned today at work. The programmer didn't have the right support disks for the SST part so I used a 29f020 part.

I wasn't sure what the differences were but I figured it would be fine for reading from it. From your post I see the difference is the voltage required for programming.

I have not tried it yet but hopefully I have undone the worst part. I was concerned about the format of the BIOS image I had being usable by the prom burner and it getting on the eprom in the correct order.I can always reprogram if I didn't get it right.

I think there is another programmer with more recent drivers in a nearby lab so I am going to check that tomorrow and see if I can get the original SST part programmed.

I have another IO on order from circuit city anyway. Truth be known, $99 isn't my most expensive door stop!

Finally, and probably of most relevance, I don't think the problem was with using the release option.

I was thinking about what I did and I think I used an incorrect flag when I wrote the image back to the flash. I think I screwed up the checksum. It seems reasonable that one of the first things the code would do is test the checksum and halt if there is not a match.

I'll post me results later.

duvell

04-03-2000 15:23:55

New MessageRE:That darn boot logo... A fix? (modified 0 times) RavTon
I had NO PROBLEM using the /release option for the logo. I did it a few days ago and it worked great. No logo at all now. At least until Win98 starts .

RavTon
ravton@yahoo.com

04-03-2000 15:42:10

New MessageRE:That darn boot logo... A fix? (modified 0 times) Fred M.
Well, since the BIOS is an 'evalution version' that is 'not for sale', perhaps modified versions can be posted on a web site. If not, maybe diff files and CRCs would help. If nothing else, the CRC from one that had the logo removed would give people a way to know for sure if they did the operation correctly.
04-03-2000 16:37:38

New MessageRE:That darn boot logo... A fix? (modified 0 times) duvell
I'm Back....

My Iopener has been brought back fom the dead. I found a couple of useful bits of information that might be of value.

I was able to burn the backup image obtained with awdflash 6.31 using a prom burner.

I had to use an AMD 29F020 part because the programmer I used did not have a driver for the SSI part. Turns out the 22F020 part uses +12v for programming while the original part the uses +5v.

I was able to boot with the newly programmed AMD 29F020 part.

I got adventurous (you'd think I'd learn!) and removed the AMD part and replaced it with the original SSI part while the system was running. I do not reccomend this. If you try this, it is at your own risk!

Despite the disclamer above, it was pretty easy. It all depends on how tight the fit is and what kind of tool you have to gently pry it out.

Once the original, and dead, bios flash chip was in, I used awdflash and restored the orginal Iopener image. I powereed down and restarted...it worked!

Once I did that I had to test the release option again. I did upgrade to cbrom 1.30 from version 1.24c. I ran it with the /logo release option. I then reprogrammed my flash with the modified image.

It worked, no logo and you see some of the bios info written to the screen, such as the HD detection.

All in all a good learning experience.

04-03-2000 19:48:59

New MessageRE:That darn boot logo... A fix? (modified 0 times) shrapnel
Alright! Way to go, guys.. A definite victory for us console OS users. I had been running Linux in framebuffer mode to overcome the graphic. No more!

And congratz, duvell.. Glad my advice wasn't entirely fatal after all. (wipes forehead with sleeve)

I think I need more expensive doorstops. My highest (that I can remember) is only $15. But since it's an external SCSI hard drive, I can sac it for the case, power supply, LEDs, etc... =)

04-03-2000 21:29:50

New MessageRE:That darn boot logo... A fix? (modified 0 times) Tackhead
duvell: Congratulations!

So to summarize: CBROM130 works, CBROM124 doesn't work, right?

(Someone else mentioned that AWDFLASH 5.xx did *not* work, because it only downloaded a 128Kx8 image, 6.31 and 7.52 gave the full 256Kx8 image.)

I do not recommend posting BIOS images, but I'd be interested in 16-bit simple checksums (like the kind you get from an EPROM burner :) of ROM images. It's possible (though not likely) that NPLI has started, or will start, serializing ROMs. (Simple enough to "flash 'em at the factory")

Posting checksums of ROM images would not, however, violate copyrights, and would allow people to determine if ROMs were being serialized.

Another thought, the various components in the flash ROM could be identical, but there's plenty of "unused space" in the flash chip. Serialization info could be crammed *there* and remain completely invisible to CBROM.

So if our ROM checksums differ from one another, we should also consider posting checksums of each ROM component.

Finally, because the 39SF020 is sector-programmable, it's just as possible that "different checksums for the ROM dump even if the CBROM components are identical" could indicate leftover crap that has nothing to do with serialization whatsoever, just a red herring.

Anyways, we don't know yet if the checksums differ, so I'll see if I can get my mitts on a friend's unit and see if his BIOS differs from mine.

04-04-2000 09:58:21

New MessageRE:That darn boot logo... A fix? (modified 0 times) Slacker
I REALLY wish I had read this thread! I tried the "/logo release" option and now my IO won't boot. No video. I had previously changed the boot logo to a tux image with no problem. Then I decided I didn't want a damn boot logo and well . . . here I am. I don't have access to an eprom burner, does anyone know of a motherboard that might support the i-openers bios chip? It doesn't look like anything I'm used to seeing in desktops. I have a backup of a working bios.

Duvell,

how much do you charge to fix a hosed bios chip? I feel like such a loser ;-<

04-06-2000 18:51:17

New MessageRE:That darn boot logo... A fix? (modified 0 times) duvell
Slacker, what's your email address?
04-06-2000 21:06:25

New MessageRE:That darn boot logo... A fix? (modified 0 times) Slacker
Duvell,

headley@viptx.net

HELP!!

04-06-2000 21:22:22

New MessageRE:That darn boot logo... A fix? (modified 0 times) Draz
Profile
I got a bit of a problem with the logo release. I got my version of the bios onto another machine over a modem (im still using qnx - dont have an hd yet) and used cbrom to release the logo. However, when I flashed the bios with the new file and rebooted, the console stayed in graphics mode. I couldnt see any text but I could type(the hd indicator light flashed when I typed in a command and hit enter) and I ended up using my hd indicator light to tell me when I had finished reflashing the bios with my backup copy. Anyone experienced a similar problem or know a fix?

Draz

10-28-2000 13:34:19

New MessageRE:That darn boot logo... A fix? (modified 0 times) tinkerer
Profile
Interesting that we're all wanting to dispense with the logo. I'm thinking of trying this, but would want to replace the logo screen with one that says "This computer is the property of (My Name)." Let 'em just TRY and delete that from the drive.
10-28-2000 22:53:14

New MessageRE:That darn boot logo... A fix? (modified 0 times) BadFlash
Profile | Email
If all that you really want to do is get rid of the I-Opener guy, go to f*r*e*e*drive.com and log in as iopener, iopener. the V5 patched image is ther last I looked with the ami flash utility that will allow you to flash a 39SF020.
* added to block the sensor.
10-29-2000 20:03:18

New MessageRE:That darn boot logo... A fix? (modified 0 times) Draz
Profile
It's not the logo that annoys me. It's the fact that I have to hold tab every time I restart. Numerous times I've had to reset the machine because i pushed the power and walked away, coming back to a scrambled screen. Anybody got any suggestions on fixing the problem I explained in my previous message?

Draz

01-19-2001 20:55:36

New MessageRE:That darn boot logo... A fix? (modified 0 times) Hous68
Profile
If you're running Linux, I posted a solution a few days ago:

http://www.linux-hacker.net/cgi-bin/UltraBoard/UltraBoard.pl?Action=ShowPost&Board=technical&Post=1959&Idle=0&Sort=0&Order=Descend&Page=0&Session=

01-19-2001 21:20:52

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