GazOS floppy driver fails in VMware

[ZetItUp]

Hi, i ported the GazOS FloppyDriver to my os.
And i was very happy when i saw that it compiled without any errors
BUT!... When i run it in VMWare, and i run init_floppy();
the virtual machine hangs and i get the error mgs:

Code: Select all

*** VMware Workstation internal monitor error ***
NOT_IMPLEMENTED vmcore/vmm/intr/apic.c:1605
Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page
 "http://www.vmware.com/info?...". Please provide us with the log file (G:\DevCenter\Camelia\vmware.log) and the core file (G:\DevCenter\Camelia\vmware-core.gz).

If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.
To collect files to submit to VMware support, run cscript vm-support.vbs.
We will respond on the basis of your support entitlement.
We appreciate your feedback,
  -- the VMware Workstation team.

Does anyone have any idea what could be wrong?

[Candy]

Hi, i ported the GazOS FloppyDriver to my os.
And i was very happy when i saw that it compiled without any errors
BUT!... When i run it in VMWare, and i run init_floppy();
the virtual machine hangs and i get the error mgs:

Code: Select all

*** VMware Workstation internal monitor error ***
NOT_IMPLEMENTED vmcore/vmm/intr/apic.c:1605
Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://www.vmware.com/info?i...". Please provide us with the log file (G:\DevCenter\Camelia\vmware.log) and the core file (G:\DevCenter\Camelia\vmware-core.gz).
If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions.
To collect files to submit to VMware support, run cscript vm-support.vbs.
We will respond on the basis of your support entitlement.
We appreciate your feedback,
  -- the VMware Workstation team.

Does anyone have any idea what could be wrong?

You write to the APIC, which doesn't understand a word of what you're saying. It's at 0xFE000000 or something near that.

Or you've discovered a real error in VMware, and you can go tell VMWare Inc that you've been able to crash their software and that they need to fix it. Note, this is only if you are VERY VERY CERTAIN that it isn't your code that's screwing up.

[giszo]

Hi!

That's a really nice message in VMware. I also saw it ( or something similar.. ) many times, but it was always the fault of my code, so i think you should re-check your code!

[ZetItUp]

Ok, thank you guys, im on my way to check my code. =)
I will return and tell the error when i found it, just if someone should have the same problem.


EDIT: Back, i found 2 errors..
1. i forgot the 'return -1' on the 'getbyte' function =)
2. Working on it.. =)

It's the reset thing..
when i use:

Code: Select all

// re-enable interrupts
outportb(0x3f2, 0x0c);

the virtual machine hungs...