Hi atreyu, I've tried your moded VBoxDD.so for 32bits Maverick with Luci (10.04 DT LTS), and it works. Thanks a lot. And I also tried to compile VirtualBox with your moded DevACPI.cpp, but cannot find VBoxDD.so output. I'd like to know it the file generated correctly, where can I find it. BTW, I've tried command: find -name "VBoxDD.so" and find -name "*.so". some other such as VBoxDDU.so can be finded.
Hi openepo, I'm glad it works, thanks 4 the info. The find command should work if you're in the build root folder, try sudo find / -name ... to do a global search
For better understanding, these hacks working temporary? Writing into memory is not persistent, did it?
Uhm...start reading, all i said is: the SLP is to long to work with the vBox config XML using the ExtraDataItem directives (at least is was to long for 3.x version, might have changed in the 4.x series) Besides above, using DMI it is in the wrong location, this oembios set requires the SLP string to be in a very specific memory range Code: F000,908A,,Windows_Virtual_XP_F9161D8E7FCC11DDBFAA369856D89593 Which translates into: start address: 000F908A, max length 104 bytes
Sorry, I never meant any offence. I really apologize. I just wanted to make things a little clearer for evil geniuses that are going to read this thread in future. And 104 is in hex that means 260 bytes BTW, I did not write 'Windows_Virtual_XP_F9161D8E7FCC11DDBFAA369856D89593' directly into memory. For some reason the memory is not writable in DMI address range too. I used 'setextradata'.
Yep, you are right. OEMBIOS.exe cannot find oem strings in memory from inside Windows. I'll test pure DOS and see if it can find them from DOS environment.