Some&nbsp; more info on this...<br>Checked the vmware logs. Following are the log entries. Hope this might offer some help to those debugging this issue. Thanks.<br><br>Jan 09 14:34:38: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xec000000(0xec000000)
<br>Jan 09 14:34:38: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xec000000(0xec000000)<br>Jan 09 14:34:38: vcpu-0| SVGA: Registering IOSpace at 0x1400 (0x0)<br>Jan 09 14:34:38: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xec000000(0xec000000)
<br>Jan 09 14:34:39: mks| VNCENCODE 1 encoding mode change: (640x480x16depth,16bpp)<br>Jan 09 14:34:40: vcpu-0| VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63 lba_cap: 16777216<br>Jan 09 14:34:42: vcpu-0| BIOS-UUID is 56 4d c8 6f 74 47 6f fb-bf fd 87 d9 7f 61 2d 9f
<br>Jan 09 14:34:42: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 0<br>Jan 09 14:34:42: vcpu-0| DISKUTIL: Offline toolsVersion = 0<br>Jan 09 14:34:42: mks| VNCENCODE 1 encoding mode change: (720x400x16depth,16bpp)<br>Jan 09 14:44:38: vmx| TOOLS setting the tools version to &#39;0&#39;
<br>Jan 09 14:44:38: vmx| VmdbDbCheckDataType failed for path=/vm/#feba309633015371/vmx/guestTools/versionStatus/ and value=notAvailable: (-11) Type mismatch<br>Jan 09 14:44:38: vmx| Vmdb_Set: Failed to set /vm/#feba309633015371/vmx/guestTools/versionStatus/ to notAvailable (Type mismatch)
<br>Jan 09 14:44:38: vmx| VMXVmdb_SetToolsVersionState failed. ret = Type mismatch<br>Jan 09 16:21:38: mks| MKS set guest selection request with invalid state 2<br>Jan 09 16:21:49: vcpu-0| CPU reset: soft<br>Jan 09 16:21:50: vcpu-0| SVGA: Unregistering IOSpace at 0x1400 (0x1400)
<br>Jan 09 16:21:50: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xec000000(0xec000000)<br>Jan 09 16:21:50: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xec000000)<br>
Jan 09 16:21:50: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)<br>Jan 09 16:21:50: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)<br>Jan 09 16:21:50: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)
<br>Jan 09 16:21:50: vcpu-0| SVGA: Registering IOSpace at 0x1400 (0x0)<br>Jan 09 16:21:50: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000)<br>Jan 09 16:21:50: mks| VNCENCODE 1 encoding mode change: (640x480x16depth,16bpp)
<br>Jan 09 16:21:51: mks| SOCKET 1 new update req with non-empty pending: logical error on server/client?<br>Jan 09 16:21:51: vcpu-0| VIDE: Curr CHS info cyls: 17475 heads: 15 sects: 63 lba_cap: 16777216<br>Jan 09 16:21:53: vcpu-0| BIOS-UUID is 56 4d c8 6f 74 47 6f fb-bf fd 87 d9 7f 61 2d 9f
<br>Jan 09 16:21:53: vcpu-0| DISKUTIL: ide0:0 : toolsVersion = 0<br>Jan 09 16:21:53: vcpu-0| DISKUTIL: Offline toolsVersion = 0<br>Jan 09 16:21:53: mks| VNCENCODE 1 encoding mode change: (720x400x16depth,16bpp<br><br><div>
<span class="gmail_quote">On 1/9/07, <b class="gmail_sendername">Muguntharaj Subramanian</b> &lt;<a href="mailto:mugunth@gmail.com">mugunth@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi All,<br>I checked out the source again yesterday and built a fresh iso (bootcd). And again i find the same issue i.e &quot;partition signature != 55AA&quot; error while trying out the created iso with VMware.<br><br>Has anybody else tried the same way? My objective is to compile the reactos iso from source first. Then plan to add applications and try to fix some bugs in my free time. For that i feel its better&nbsp; to use VMware instead of running fresh install (also i dont have spare machine to do fresh installation).
<br><br>Is the current builds working in QEMU?&nbsp; <br><br>Regards,<br>Mugunth<div><span class="e" id="q_11005b80cdb38e60_1"><br><br><div><span class="gmail_quote">On 1/8/07, <b class="gmail_sendername">Mikhail Y. Zvyozdochkin
</b> &lt;<a href="mailto:mzvyozd@narod.ru" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mzvyozd@narod.ru
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Felipe Villarroel wrote:<br><br>&gt;On 1/5/07, Muguntharaj Subramanian &lt;
<a href="mailto:mugunth@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mugunth@gmail.com</a>&gt; wrote:<br>&gt;<br>&gt;<br>&gt;&gt;...<br>&gt;&gt;partition signature != 55AA<br>&gt;&gt;...
<br>&gt;&gt;<br>&gt;&gt;<br>&gt;You have a corrupted MBR or partition table. Reinstall ReactOS and do
<br>&gt;proper partitioning.<br>&gt;<br>&gt;<br>Hm, Hm... It&#39;s not so simply.<br>I got same error with _fresh-installed_ ReactOS.<br><br>WBR, DarkHobbit<br><br>_______________________________________________<br>Ros-dev mailing list
<br><a href="mailto:Ros-dev@reactos.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Ros-dev@reactos.org</a><br><a href="http://www.reactos.org/mailman/listinfo/ros-dev" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.reactos.org/mailman/listinfo/ros-dev</a><br></blockquote></div><br><br clear="all"><br></span></div><span class="q">
-- <br><br><a href="http://mugunth.blogspot.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://mugunth.blogspot.com</a><br><a href="http://thamizha.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://thamizha.com</a><br></span><a href="http://tamilblogs.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://tamilblogs.com</a><br><span class="sg"><br><br>-- <br><a href="http://webspace2host.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">

http://webspace2host.com</a><br>&quot;Your friendly hosting provider&quot;

</span></blockquote></div><br><br clear="all"><br>-- <br><br><a href="http://mugunth.blogspot.com">http://mugunth.blogspot.com</a><br><a href="http://thamizha.com">http://thamizha.com</a><br><a href="http://tamilblogs.com">
http://tamilblogs.com</a><br><br><br>-- <br><a href="http://webspace2host.com">http://webspace2host.com</a><br>&quot;Your friendly hosting provider&quot;