Build Your Own Arcade Controls Forum

Main => Main Forum => Topic started by: shrunkenmaster on September 01, 2009, 03:21:51 pm

Title: Emachines 480 - can't use Bootskin
Post by: shrunkenmaster on September 01, 2009, 03:21:51 pm
Currently (trying) to build a bartop with an EMachines 480 motherboard donated by my dad. Bootskin flatly refuses to show anything but the default - any ideas? Also, the mobo shows an Emachines splash screen right at the start of booting (before anything else) - there's nothing in the BIOS to get rid of it. Would love to get rid of this too.
Title: Re: Emachines 480 - can't use Bootskin
Post by: severdhed on September 01, 2009, 06:54:18 pm
as for the bios splash screen, you are probably stuck with it.  bootskin however should not care what hardware you have.  did you try removing it and reinstalling?  or perhaps try a different skin?   i am assuming you are using windows xp...correct?
Title: Re: Emachines 480 - can't use Bootskin
Post by: DJ_Izumi on September 01, 2009, 08:31:01 pm
The eMachines boot logo is built into the system firmware.  eMachines may offer a tool for altering or replacing that image, but it could vary by model.

I had an old eMachines eMonster 500A that featured the eMachine boot logo and all eMachine's issued mobo firmwares featured it.  However I had to dig up a newer firmware issued by the motherboard OEM for it's Napoli-3 Motherboard to make the mobo work with a Radeon VE/7000 card.  This was from the Japanese company and not by eMachines, after flashing this firmware on the eMachines logo was gone.

On my current mobo from Asus however, Asus actually has a formal tool where I can add any 256 color 640x480 bitmap to the firmware, but that's a 'feature' from Asus.
Title: Re: Emachines 480 - can't use Bootskin
Post by: david656 on September 01, 2009, 09:22:20 pm
It may sound silly but i had a .... eci..msi board? and bootskin wouldn't work on that atall.. i formatted the hard drive and made boot skin the first thing i installed after direct x or something and it worked ! a re-install of xp may just sort it