smbios with vmware missing info?

[supagu]

im using vmware in windows for OS dev, when i go to get some info it appears to be invalid or missing.

for example, it says my FSB is 0
i get nothing for types 16 or 17 (Memory stuff), so i can determine how much memory i have

:-/

any one have a similar experience?

[Jeko]

im using vmware in windows for OS dev, when i go to get some info it appears to be invalid or missing.

for example, it says my FSB is 0
i get nothing for types 16 or 17 (Memory stuff), so i can determine how much memory i have

:-/

any one have a similar experience?

I don't know. But could you send me your source code about smbios? Or could you give me some links about smbios programming?

[Kevin McGuire]

im using vmware in windows for OS dev, when i go to get some info it appears to be invalid or missing.

for example, it says my FSB is 0
i get nothing for types 16 or 17 (Memory stuff), so i can determine how much memory i have

:-/

any one have a similar experience?

I think you might not understand how to ask a question that we can actually understand and solve in less than four hours unless you get lucky and someone is working on that exact same problem which is unlikely.

I have no idea what FSB could stand for. You could have given us more information about the FSB in you're context of it.

This will help you get help on SMBIOS.
http://www.catb.org/~esr/faqs/smart-que ... #beprecise
These three are related to each other.
(and yes the first link below is a post you made with out any replies)
http://www.osdev.org/phpBB2/viewtopic.php?t=13720
http://www.catb.org/~esr/faqs/smart-questions.html#code
http://www.catb.org/~esr/faqs/smart-que ... tml#volume

You asked a smart question which is why it says smart-questions in the uniform resource identifiers. Good Job.

[Brendan]

Hi,

im using vmware in windows for OS dev, when i go to get some info it appears to be invalid or missing.

Imagine you're in charge of maintaining the hardware for 200 computers and need to know what is in each computer for repairs, upgrades, etc. You could go to each computer, pull it apart and try to figure things out what each part is, then manually enter the information into a database. This is time consuming and doesn't work for some information. For example, consider trying to find out the front side bus speed by examining the motherboard and CPU - you'd ned to remove the CPU fan, wipe away enough of the white heatsink grease to read the CPU's details, then look up the CPU's information (and then you'd only have the speed the CPU was intended for and not the speed it's actually using - it could be underclocked or overclocked).

This is what SMBIOS is for - it's intended for system administrators to use (via. some form of software) for system management (i.e. maintaining a list of hardware to make it easier to handle upgrades, repairs, determine what spare parts are worth keeping on hand, etc) . For an example, on a Windows network you could setup the server/s to make client machines download and run a "SMBIOS client" and upload this information into a database.

So, what hardware should an emulator like VMware report to these system administrators? IMHO it should report nothing as none of the hardware is real hardware - it's all "virtual" hardware that doesn't actually exist.

i get nothing for types 16 or 17 (Memory stuff), so i can determine how much memory i have

Use something designed for OSs to rely on for memory detection (for e.g. BIOS memory size functions like "INT 0x15, EAX =0xE820"), rather than something that isn't intended for OSs to rely on.


Cheers,

Brendan

[xsix]

one thing is that virtual machines doesn't emulate real hardware in 100%. Maybe that's why you don't get needed information. Another thing is memory, it's much easier to use CMOS(if memory<64mb) and BIOS if you want to find memory >64 as said above

[inflater]

I have no idea what FSB could stand for

FSB = Front Side Bus.
http://en.wikipedia.org/wiki/Front_Side_Bus

inflater