Can anyone tell me what this is and what it does please?
LAN 'BOOT ROM' IN ASUS MAINBOARD BIOS?
cheers!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
What that does is so you can "wake" your computer up through the network. It will pull a computer out of standby or hibernation. The ability to switch on remote computers through special network packets. This only works with network cards and motherboards that are Wake on LAN compliant, which your's does. Even though the machine is turned off, the network card still listens for that "magic" packet that will tell it to turn on. Hope this helps.
hi,
a bios rom/rompaq is just a bios ,"lan boot rom" option is not only in asus mainboards,it describes the bios that commands the access method from the network to your motherboard,in other words if the option is enabled ,your motherboard is awaiting for a signal from the network to be set to boot up and additionally the machine could be exploited,another standart option is "boot on lan",,,,
if you have network and you want to command the different workstations from a very pc you can use this option to get access on a pc belonging to your network,the rom is only the interface which can translate adequate the prtocols to the remote machine,so you can establish the remote control over the machine,,,
check out the followig link:
http://www.logicsupply.com
cu
To be honest I don't fully understand either but I thought Boot ROM and WOL were quite different.
As I understood it WOL was used to remotely boot a configured system and Boot ROM or PXE was to locally boot an un-configured system from the network. I am aware they can be combined as well. Please feel free to correct/educate me.
From: http://searchwin2000.techt
WOL:
"Wake on LAN is a technology that allows a network professional to remotely power on a computer or to wake it up from sleep mode . By remotely triggering the computer to wake up and perform scheduled maintenance tasks, ..."
Boot ROM or PXE:
Preboot Execution Environment (PXE) refers to various methods of getting an IBM-compatible computer, typically running Windows, to boot up without the need for a hard drive or boot diskette. The methods evolved from the era before computers had internal disk drives. PXE usually involves booting a computer from firmware -- data contained on a read-only-memory (ROM) or programmable read-only-memory (PROM) chip -- rather than from data contained on magnetic media. This gives rise to the terms 'PXE boot ROM' or 'PXE boot PROM' (sometimes written 'PXE bootprom'). Booting from ROM or PROM eliminates the reliance on an electromechanical device (the physical drive). This enhances reliability and eliminates drive read errors. With today's memory technology, booting from ROM or PROM is fast. PXE can be also used to boot a computer from a network.
RobWill's answer is correct. Boot ROM used to appear on all network cards, at least those that copied the first Novell design. Computers with built-in NIC would need a socket for the boot ROOM as well for full compatibility.
Basically it's like a super version of DHCP. In DHCP, your computer sends a signal to the network and contacts the DHCP "server", who then tells your computer to use this-and-that settings, so you can connect. Boot ROM is kinda like that. Like the BIOS ROM, it loads the PC, sends a signal out to network, and the appropriate server will say "boot using this boot disk image" and it'll load that image as if it's a real hard drive, albeit at network speeds. Thus, the machine doesn't need a floppy or a hard drive, as EVERYTHING (even the user directory) is on the network, thus the term "diskless workstation".
....as it's ROM and not PROML i.e. read only - it can't be instructed/programmed to look for "the appropriate server"!
In this case what is the appropriate server and where is it located?
what instruction is in the signal?
I am assuming this would be in a LAN of say 3 or 4 PC's for instance?
What if all the other PC's on the LAN respond to the signal! - surely only one other PC can boot the PC that transmits the signal?
....not with it yet :(
I'm getting in way over my head here, and may be totally wrong but what I have absorbed to date about this, right or wrong is:
>>"....as it's ROM and not PROML i.e. read only - it can't be instructed/programmed to look for "the appropriate server"! "
As I understand it the ROM is pre programmed/flashed to look for a particular set of boot instructions from a BOOTP server. This whole scenario will on work of course in an environment configured for what is currently called PXE boot sequence, which requires a BOOTP server to be configured and advertised on your network. Usually the DHCP server does this but it is a separate configuration from the basic DHCP scope.
>>"what instruction is in the signal?"
I really don't know. Perhaps someone else can shed some light on that. Apparently, the NIC looks for an advertised BOOTP server, requests an IP, the server assigns the IP and some basic connection information, enough for the workstation to connect to a network share containing the OS install files.
>>"I am assuming this would be in a LAN of say 3 or 4 PC's for instance?"
I thought it was primarily used in large corporate environments.
>>"What if all the other PC's on the LAN respond to the signal! - surely only one other PC can boot the PC that transmits the signal"
Again, I don't know how it works, but there is a standard as to how the network and NIC have to be configured since there is very little room for negation. I believe it is RFC-951 that addresses this, but I have never read it.
This question has been classified abandoned. I will make a recommendation to the moderators on its resolution in a week or two. I appreciate any comments that would help me to make a recommendation.
Unless it is clear to me that the question has been answered I will recommend delete. It is possible that a Grade less than A will be given if no expert makes a case for an A grade. It is assumed that any participant not responding to this request is no longer interested in its final disposition.
If the user does not know how to close the question, the options are here:
http://www.experts-exchang
compfixer101
EE Cleanup Volunteer
Business Accounts
Answer for Membership
by: RobWillPosted on 2005-07-29 at 20:19:07ID: 14560046
"A boot ROM lets you set up a diskless workstation on the network. By installing a boot ROM in the network board, you can make your computer load DOS from a network file server, instead of a local disk drive."
Basically if configured correctly your computer can boot from the NIC with no operating system installed on the local workstation. This is how many large networks boot and install their initial Windows and supplementary applications on a new workstation.