Want to work on subsystem
Moderator: Moderator Team
Want to work on subsystem
Hello
I have been reading ReactOS forum on and off and have tried ReactOS with Bochs and Qemu (it works fine).
I want to work on ReactOS DOS subsystem, so I tried ROS Live CD on my notebook (PIII750, S3 savage graphics card), the only machine I can experiment with.
After the Blue boot screen nothing happens. I think, it must be some driver problem.
Can somebody please guide me what are the correct steps to make ReactOS work?
I have been reading ReactOS forum on and off and have tried ReactOS with Bochs and Qemu (it works fine).
I want to work on ReactOS DOS subsystem, so I tried ROS Live CD on my notebook (PIII750, S3 savage graphics card), the only machine I can experiment with.
After the Blue boot screen nothing happens. I think, it must be some driver problem.
Can somebody please guide me what are the correct steps to make ReactOS work?
HI
S3 savage graphics card some version of that card did come with
vbe 1.2 so reactos vbe 2.0 driver does not work fine with all version of
S3 savage graphics card. It did exists some 3d part flash bios file to that card to upgrad it to vbe 2.0 standard or vbe 3.0 standard.
I do not know if that is your case or not.
S3 savage graphics card some version of that card did come with
vbe 1.2 so reactos vbe 2.0 driver does not work fine with all version of
S3 savage graphics card. It did exists some 3d part flash bios file to that card to upgrad it to vbe 2.0 standard or vbe 3.0 standard.
I do not know if that is your case or not.
Thank you for the information. Anyway, I am trying to get a grip on the ReactOS souce code now.
Also, I am using ReatOS with Qemu to see it in action.
Though I am trying to understand the overall system, but I am giving special attention to src/subsys folder as that is the area I'll be working on if possible.
Also, I am using ReatOS with Qemu to see it in action.
Though I am trying to understand the overall system, but I am giving special attention to src/subsys folder as that is the area I'll be working on if possible.
-
- Posts: 115
- Joined: Wed Jan 05, 2005 10:53 pm
- Location: a thousand miles from Hinterland
- Contact:
I'm working on a DOS protected mode emulator called Protos (no real mode, just protected mode). It should be able to work on both Windows and ReactOS.
It's still in early development and might never get done, but I've outlined the overall structure of the system, and it seems like a good idea to me
Tell me if your interested. Maybe we can work on a full emulator together.
It's still in early development and might never get done, but I've outlined the overall structure of the system, and it seems like a good idea to me
Tell me if your interested. Maybe we can work on a full emulator together.
caveman LIKES chocolate.
we shall reinvent the wheel until it turns properly.
we shall reinvent the wheel until it turns properly.
-
- Posts: 115
- Joined: Wed Jan 05, 2005 10:53 pm
- Location: a thousand miles from Hinterland
- Contact:
Really different. Mine is only an application-level emulator (I mentioned it should work under windows, as well).Just out of curiosity may I ask, how different is your implementation (and future ideas) from FreeDOS?
Because of the lack of it. Most emulators don't support it (because of complexity). And the most troublesome DOS progs to get going are protected mode ones.Why have you chosen on Protected mode implementation?
My idea is based a little on VDMSound (google it if you haven't heard of it before).
caveman LIKES chocolate.
we shall reinvent the wheel until it turns properly.
we shall reinvent the wheel until it turns properly.
-
- Posts: 115
- Joined: Wed Jan 05, 2005 10:53 pm
- Location: a thousand miles from Hinterland
- Contact:
(from the dosbox site)
This is what i'm talking about.
VESA/SVGA 70% implemented VBE 2.0 support with 256 color modes
Rarely needed? Doom. Doom II. Duke Nukem. Shadow Warrior. Terminal Velocity. Quake. All use DPMI.DPMI 80% implemented Disabled. As it's rarely needed.
This is what i'm talking about.
caveman LIKES chocolate.
we shall reinvent the wheel until it turns properly.
we shall reinvent the wheel until it turns properly.
currently, I am looking at "dosbox", "FreeDos" and "DosEMU".
From DosEMU site
I am aslo reading about vdmsound to understand your idea.
Let's pick the best option for ReactOS DOS subsystem and start working when we are ready
From DosEMU site
AcetoliNeDOSEMU stands for DOS Emulation, and is a linux application that enables the Linux OS to boot any DOS and run DOS programs - including DPMI applications
I am aslo reading about vdmsound to understand your idea.
Let's pick the best option for ReactOS DOS subsystem and start working when we are ready
I'd say running FreeDOS in the same way as CoLinux, and extending out stuff like the filesystem from the ROS kernel, etc, would work a lot better than any emulator. You have to do some address translations, etc, but a lot of stuff you should be able to keep native. Why would a DOS subsystem have to be an x86 emulator if the host platform IS x86?
Not realy sure about that becouse serious crash in coLinuxmf wrote:I'd say running FreeDOS in the same way as CoLinux, and extending out stuff like the filesystem from the ROS kernel, etc, would work a lot better than any emulator.
will cause crash of whole system. (but of course perfomance is outstanding).
IMHO system stability should be at first place.
BTW what is current status of coLinux and ReactOS?
IIRC year ago Dan Aloni (coLinux creator) offered his help for porting but
there there was some internal problems with ReactoOS which stoped
coLinux from runing. Does anything changed now?
-
- Posts: 115
- Joined: Wed Jan 05, 2005 10:53 pm
- Location: a thousand miles from Hinterland
- Contact:
That's exactly what I thought. My idea (Protos) is a little bit different, but similar to freedos and dosemu.I'd say running FreeDOS in the same way as CoLinux, and extending out stuff like the filesystem from the ROS kernel, etc, would work a lot better than any emulator. You have to do some address translations, etc, but a lot of stuff you should be able to keep native. Why would a DOS subsystem have to be an x86 emulator if the host platform IS x86?
Not realy sure about that becouse serious crash in coLinux
will cause crash of whole system.
You're quite right. But shouldn't we leave choosing between system stability and speed up to the user? Making assumptions about what the user wants sounds too much like the big companie$ .IMHO system stability should be at first place.
azeemarif: did you check out ntvdm.c (reactos\subsys\win3k\ntvdm\ntvdm.c)?
That's basically all there is to virtual DOS in reactos!!! It NEEDS to be improved.
If we want to get started, you can email me about your stuff (my email is in my profile) and I'll tell you about what I've done so far (which is far too little ).
I'll have to do it in my spare time -- right now I'm struggling with implementing an alphablend into ros gdi...
caveman LIKES chocolate.
we shall reinvent the wheel until it turns properly.
we shall reinvent the wheel until it turns properly.
Who is online
Users browsing this forum: DotBot [Crawler], Yandex [Bot] and 41 guests