G41M-E43 and BIOS BOOT IMAGE

Does anyone know if this board can have it's BIOS BOOT image replced with a custom one?
What tool is used to do this?
I would like to change the image to something for my HTPC I am building....I know I can disable it. I want to put my own image on the BOOT screen.
Thanks,
*BH*

ThinkWiki says you have to work with them. I haven't come across a method to suppress them.
http://www.thinkwiki.org/wiki/How_to_change_the_BIOS_bootsplash_screen
I don't work for Lenovo. I'm a crazy volunteer!

Similar Messages

Changing bios boot image

Are there any tools in order to change the bios boot image. I would like to change the default image for a custom one.
My motherboard is a MSI MS-7071 (PM8M2-V)
Thanks
Paul

hi there, welcome to forum.
if you are talking about custom logos,(if not explain better what you have try to do) have a look here: https://forum-en.msi.com/index.php?topic=103944.msg764287#msg764287
but remember any BIOS modifycation has to use at own risk.

Setting up an Image Server and Selecting boot Images

I am setting up my first image server and when i perform a network boot I can see that i am reaching the DHCP server but i dont i am not getting a boot image. I have configured the server with an install image and a boot image but still getting nothing.
Can someone please help a novice set up this server.

If this is for ConfigMgr enter the following in your DHCP
Option 066 - the FQDN of your SCCM server.
Option 067 - the path smsboot\x86\wdsnbp.com
Cheers
Paul | sccmentor.wordpress.com

R2 upgrade and custome boot images

Hi Guys
What happens to the custom boot images after the upgrade to R2 from SP1? There are some boot images customised to be able to connect to 802.1x secured wired network and I was wondering what will happen to them after upgrade?

They're not gone after the upgrade so there's nothing to re-import thus yes you can still use them although boot images based on WinPE 4.0 are not technically supported in R2 (though they should work). You won't be able to add drivers to them or
maintain them in the console either. You should put in the effort to customize WinPE 5.0 based boot images for the long run though.
Also note that Win8 won't be supported anymore after October of this year (http://support.microsoft.com/lifecycle/search/default.aspx?alpha=Windows+8&Filter=FilterNO&wa=wsignin1.0) so
you should plan to move to Win 8.1 Update ASAP for your deployments.
Jason | http://blog.configmgrftw.com

Mdt integration boot image and SCCM boot image

I created a MDT task sequence in SCCM and went through all the steps for setting up the toolkit and settings and boot image. After all that, I distributed everything to my DP. When i try to boot to pxe and run that new MDT task sequence it finds the pxe
server, but just sits at "Contacting server" for some time until it times out. If I select the SCCM boot image in the task sequence properties then it works. the one created when i create the task sequence doesn't.
Any Idea?

Sounds like you didn't enable the boot image for PXE. This is a checkbox at the bottom of the Data Source page in the properties of the boot image.
Have you reviewed smspxe.log?
Jason | http://blog.configmgrftw.com | @jasonsandys

Macbook switch efi and bios boot

Hi guys.
First of all, thank you for the nice installation-tutorials, but i got stuck at this point.
my situation is:
I have successfully installed arch with kde on my MacBook 8,2.
After some tweeking i got grub booting arch with efi, but i had to add these parameter: "radeon.modeset=0 i915.modeset=0"
It works pretty well, but i cant access the AMD graphic card, because i need to boot over bios, and thats my question...
How do i boot into bios? do i have to update the grub config? I have no idea how to handle this.
I hope that someone can help me.
cheers
Moesi

You can't "boot GRUB to BIOS" per se. Any given build of GRUB is either EFI and therefore supports EFI-mode booting or is BIOS and therefore supports BIOS-mode booting. Thus, to boot in BIOS/CSM/legacy mode, you must install the BIOS version of GRUB. On a Mac, you must also create a hybrid MBR. You'll also have to have a boot manager that supports switching boot modes. The Apple's EFI can do this when you hold down Option/Alt on boot, or you can install rEFInd (or the earlier rEFIt, but it's not been updated in years).
Overall, if you can get your video working in an EFI-mode boot, that's the superior option. A BIOS-mode boot of a Mac just involves too many ugly hacks that are likely to come back to haunt you in the future.

Do I need to use a boot image? 6509 / Sup2T Quad / VSS

I'm curious about boot loader images and if or why I should use one.
I've got a 6509 VSS setup running right now with no bootloader variable and no boot image.
SHEC-VSS#sh boot
BOOT variable =
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby BOOT variable =
Standby CONFIG_FILE variable =
Standby BOOTLDR variable =
Standby Configuration register is 0x2102
SWITCH-VSS#sh ver
Cisco IOS Software, s2t54 Software (s2t54-ADVIPSERVICESK9-M), Version 15.1(2)SY2, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Wed 26-Feb-14 16:03 by prod_rel_team
ROM: System Bootstrap, Version 12.2(50r)SYS3, RELEASE SOFTWARE (fc1)
SHEC-VSS uptime is 16 weeks, 3 days, 21 hours, 10 minutes
Uptime for this control processor is 16 weeks, 3 days, 21 hours, 10 minutes
System returned to ROM by power on
System restarted at 13:56:56 CDT Fri May 16 2014
System image file is "bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin"
Last reload reason: power-on
I'm about to set up a nearly identical VSS pair for another facility.
I just downloaded the latest SY3 version of IOS for the new pair, and there is a boot image available:
s2t54-boot-mz.SPA.151-2.SY3.bin
I just don't know why I would want or need that. Can anyone explain? I'm not a newbie by any means, but I just don't know why I'd need it. Right now, in the bootdisk: volume, I just have my IOS image: s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin That was all that was in there before, but now that I'm building this new pair, I copied s2t54-advipservicesk9-mz.SPA.151-2.SY3.bin onto the same volume.
I understand that if I set a boot variable I can tell it to boot from one image or the other, but what does the BOOTLDR variable do for me. If I were to set the BOOTLDR variable to bootdisk:/s2t54-boot-mz.SPA.151-2.SY3.bin then what does that do for me? Right now, if I reboot, (until I added that 2nd image) it will just boot the only image in that directory with no issue.
What am I missing? Do I need to upgrade or use this boot image for anything?
Thanks for any tips you can provide!
Tim

Tim,
In simple terms, the bootldr file is the helper file to load the IOS.
The BOOTLDR environment variable specifies the Flash file system and filename that contains the boot loader image required to load system software.
The variable defines the primary Cisco IOS image that will load the final image from another source.
we need to set the BOOTLDR environment variable to specify the Flash device and filename of the boot loader image.
For Old version of IOS, there is a requirement of boot loader image to boot up the IOS image.
But for the latest version of IOS, no need for boot loader image.
Below are few things happen when the device boots:-
1. The router initially boots into ROMMON (this is your bootstrap code, which you can see in the show version command).
2. Then the router loads into the bootloader code (this is the bootloadr code, which you see in show version). This bootloader code is just an intermediate step between the ROMMON mode and the IOS mode.
3. The router then boots into the IOS mode from the bootloadr mode.
So if you do not mention the bootloadr specifically by giving the "boot bootloadr" command, the router will assume the bootloadr to be in bootflash of the device and try to boot it from there. If you mention the "boot bootloadr flash:...." command, then the router will look for the bootloadr in the flash (instead of the bootflash). Thats the only difference.
However, in both cases, if you have a valid IOS to boot into, then the router will come up without a problem, irrespective of the fact whether bootloadr image is in bootflash or flash.
HTH
REgards
Inayath
*Plz dont forget to rate if this info is helpfull.

Boot Image - Driver Path

I have another question on drivers and the boot image. I changed the UNC path of a driver and updated the driver itself with the new path. I thought all was good however that driver is in one of my boot images and now I am unable to update the
DP with the boot image as it fail for a that driver with the old path... I verified that the driver in the drivers list has the new path however the boot image still see the 'old' path. this does not make since as I would assume it would just reference
the 'driver' and thus see the new path but I guess it holds its own driver information?.. weird
Is there anyway to see/change the path of a driver listed in the boot image?

Hi,
Based on my test, you could resolve this issue by delete the driver from the list and re-add it.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 Matching Processor Architecture Boot Image (0) not found

SCCM2012 SP1 ,One Site, 3DP.
one DP can not install os with PXE boot. when start PXE F12, system crush with code 0x00000f. and Log like this
"00:0C:29:90:D1:C0, 291241B9-AB25-4400-B746-99E018F70F1A: device is in the database. SMSPXE 2014/10/1 2:28:11 4504 (0x1198)
Warning: Matching Processor Architecture Boot Image (0) not found SMSPXE 2014/10/1 2:28:11 4504 (0x1198)"
The BOOT.wim file works well in ither DP.
I have try to redeploment the PXE and reload the Boot.Wim file in this DP, but can not reslove this problem.
I'm afried reset the Boot.wim will take other 2 DP can not work too.
Please Help.

Hi Pazza,
As Torsten said, please ensure that you have an x86 and x64 boot image configured and deployed, regardless of the architecture of the OS that
you wish to deploy. Secondly, ensure that the boot images for both architectures have the network drivers for the respective model that you are imaging injected.
Otherwise, please review the link below:
ConfigMgr PXE Boot Warning: Matching Processor Architecture Boot Image (0) not found
http://www.systemcentercentral.com/configmgr-pxe-boot-warning-matching-processor-architecture-boot-image-0-not-found/
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Boot image does not exist and cannot read disk label errors.

Hi - I'm having a problem with installing Solaris 9 4/04 on a Netra T1. The Netra already has Solaris 7. I need to get this set up as a jumpstart server but it can't find the boot image. I'm using a brand new bonafide installation disk - not a copy. The system won't let me install/upgrade to Solaris 9 either. I get an error stating that disk label can't be read. I've tried swapping out the CDROM but I still get the same errors. Does anyone know what or why this may be happening? (Oh - and another strange thing - like I said the CDs are the original but there doesn't appear to be a cdrom/cdrom0/s0 directory. The directory I see is cdrom/cdrom0/sol_9_404_sparc/Solaris_9/Tools)
ERROR: Install boot image /cdrom/sol_9_404_sparc/Solaris_9/Tools/Boot does not exist
Check that boot image exists, or use [-t] to
specify a valid boot image elsewhere.
and
Excuting last command: boot cdrom [- nowin]
Boot device: /pci@1f,0/pc1@1/ide/cdrom@2:f file and args: [- nowin]
Can't read disk label.
Can't open disk label package
Evaulating: boot cdrom [- nowin]@1/ide@e/cdrom@2:f File and args: [- nowin]
Can't open boot device
I appreciate any help at all - is there anyone out there who can tell me what I may be doing wrong?
Thanks

Hi check that you are booting of the right cd. Make sure it is soalris 9 software 1/2 if that fails then it may well be that your cd is buggered. most likely it is buggered it it cant find the boot image.

I was using bootcamp assistant to install windows 7 via flash drive, i followed the steps, the Windows installation image was installed successfully and the boot camp partition was made andy mac restarted then i got this message "no bootable device insert

"..no bootable device insert boot disk and press any key", i restarted my mac and held options and managed to log in to my OS x again but my windows wasn't installed and when i held options while my mac was starting the usb flash drive wasn't there, what should i do? Also can i restore my usb flash drive to use it as a regular flash drive again?

Hi Michael!
Yep, I did get this running. Not in a normal way (meaning the easy way). What I did, is that I just created the BOOTCAMP partition in OS X. Just let it format and create the partition where you would install BOOTCAMP.
After that I discovered that via a ISO program (WinClone) you can directly restore a previously created OS X boot image to your current computer. So, I installed a blank Windows 7 to my macbook pro, didint install any drivers and just let it work up then. Then I went back to os X (in macbook pro) and made a bootimage for the BOOTCAMP partition. After that I saved it to my external harddrive and wired it to my iMac. In iMac I just downloaded the same boot-image program and restored the bootimage that I made in Macbook Pro to iMac. After that I made an restart and the bootcamp section with windows worked well with my iMac. Install the bootcamp soft and you can do everything and everything works. FYI, you get the windows working via those steps, BUT if you either delete or do anything to make your bootcamp partition unworkable then you will have to repeat those steps again. But it´s fast non-the-less, so it shouldn´t be a problem for you.
If you didin´t understand anything or something doesen´t add up, send me a letter or a notification.
Hope this helps.
Indrek.

MDT boot image and when we try to PXE boot it won't get the IP Address.

We created a custom MDT boot image and when we try to PXE boot it won't get the IP Address.
I press F8 and type IPCONFIG we get Windows IP Configuration. We are using vmxnet3 network adapter.
I think I need to inject 32-bit vmxnet3 driver to the custom MDT boot image which is 32-bit.
We are using it to deploy Windows Server 2008 R2 with SP1 operating System.
Can I just use the 32-bit custom MDT boot image or do I need to use 64-bit Custom MDT Boot Image?
Also Is there a blog on how to inject vmxnet3 driver to boot image?

You can try this:
http://mwesterink.wordpress.com/2013/12/03/configmgr-2012-obtaining-vmxnet3-nic-drivers-for-vmware-virtual-machines/
Honestly, your best bet is to use a different adapter (E1000). I personally have had no luck getting the vmxnet3 driver to work properly in WinPE. It's either really, really slow or it simply doesn't load at all.

Upgrade to SCCM R2 have to recreate boot image and TS

Wanna ask, I have upgraded from my SCCM from SP1 CU3 to R2. But i noticed that in boot image, the WinPE tab is missing thus i cannot include the network driver. Anyway that i can make the tab reappear again? Net says have to recreate the boot image and TS...
http://www.deploymentresearch.com/Research/tabid/62/EntryId/117/A-Geeks-Guide-for-upgrading-to-ConfigMgr-2012-R2-and-MDT-2013.aspx

This often happens after R2 upgrade. If your boot image does not have 6.3.9600 version then you will not be able to manipulate it using the R2 console. You don't need MDT to create a new one though (this new version).
You can use dism. See here. It's very easy. I had to do it yesterday.
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Task Sequence Failing after Stating Boot Image and Restart in WinPE - Windows XP to Windows 7

Good Morning,
I am trying to upgrade an XP Machine to Windows 7 (x86). I was using the boot image inbuilt with SCCM 2012 R2 but read that it wont work correcltly. I am using Windows PE 3.1 boot image to boot.
The TS fails after trying to restart in Windows PE when staging the boot image.
From the Logs in CCM\Logs\SMSTSLog
I am still getting the same issue as when i am using the Boot image from ADK 8.1.
Anybody has an idea on how to solve this issue ? I have read a workaround about replacing the bootsect from the boot image but funily i am using an older boot image.
Kind Regards,
Mathieu

http://support.microsoft.com/kb/2910552
Torsten Meringer | http://www.mssccmfaq.de

Can't update BIOS boot logo

Hi,
I've tried changing the BIOS boot logo of my Thinkpad E420, but a specific image isn't working, for some reason. I use the last "BIOS update utility", being 1.26, from here. No error shows up during the upgrade.
http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&DocID=HT037710
This is what I should do to change the BIOS Logo:
* NOTES ON CUSTOM START UP IMAGE                                    *
* THIS VERSION OF THE FLASH UPDATE PROGRAM GIVES THE OPTION OF      *
* REPLACING (OR ELIMINATING) THE DEFAULT "LENOVO" IMAGE THAT IS     *
* DISPLAYED DURING SYSTEM START UP.                                 *
* GUIDELINES FOR CUSTOM START UP IMAGE:                             *
* 1. THE IMAGE FILE SIZE IS LIMITED TO 30KB.                        *
* 2. RESOLUTION OF THE IMAGE SHOULD BE LESS THAN 640X480.           *
* 3. VALID FORMATS FOR THE IMAGE ARE AS FOLLOWS:                    *
*        BITMAP (.BMP) FILE FORMAT                                   *
*        JPEG (.JPG) FILE FORMAT                                     *
*        GIF (.GIF) FILE FORMAT                                      *
* STEPS TO ENABLE CUSTOM START UP IMAGE:                            *
* 1. PREPARE YOUR IMAGE AND COPY IT TO THE SAME PLACE WHERE         *
*     WINUPTP.EXE EXISTS.                                            *
* 2. RENAME THE IMAGE AS FOLLOWS.                                   *
*         BITMAP FILE --> LOGO.BMP                                   *
*         JPEG FILE --> LOGO.JPG                                     *
*         GIF FILE --> LOGO.GIF                                      *
* 3. RUN WINUPTP.EXE AND FOLLOW INSTRUCTIONS.                       *
* AFTER YOU UPDATE THE BIOS ON YOUR SYSTEM, YOUR LOGO WILL          *
* APPEAR ON THE STARTUP SCREEN.                                     *
Interestingly, this image work as it should:
https://www.dropbox.com/s/600u9o08a1ax1wp/LOGO_OLD.jpg
But this one don't:
https://www.dropbox.com/s/hrayfjslyv57o53/LOGO.JPG
I never get any error during the update, I click "YES" on the popup "Custom image was found, do you want to use it", but if I chose the second image, I get a black screen at the BIOS logo (Computer continue booting normally, and I can access the BIOS - but I have a black screen).
What's wrong with the second image? How is the second image different from the first one, that does work? I don't get it. :/
I can also succesfully restore the BIOS logo to the Default, if I delete LOGO.JPG from the update folder.
Thanks for the help.

Hi GameX,
the only difference that I can see immediately is something which caused me problems with a particular web publishing software once, took me ages to find the bug. Your second picture has JPG as the ending, the first jpg - maybe the utility is case sensitive on file endings??
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

G41M-E43 and BIOS BOOT IMAGE

Similar Messages

Maybe you are looking for