Serial mouse under 0.3 RC1

Ask your support questions in here

Moderator: Moderator Team

Post Reply
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Serial mouse under 0.3 RC1

Post by Tiansen »

I'm trying to use serial mouse under ReactOS 0.3.0 RC1. It just doesn't work. Isn't it supposed to work? It's on COM1. Do I have to do someting?

If I try to boot Knoppix, mouse works fine.
Davy
Posts: 18
Joined: Sat Jan 07, 2006 10:39 pm

Post by Davy »

It should work, unless the mouse needs it's own drivers.

You should reinstall ReactOS and check to see if the configuration is set to Serial Mouse (if you are using the Install CD one) otherwise you may have to use it's own drivers on it (which could/couldn't work) reason I speak that was is because there are some drivers that still don't work yet.
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

Where to check that? During installation there are only keyboard settings.
User avatar
Jaix
Moderator Team
Posts: 838
Joined: Sat Nov 27, 2004 3:40 pm
Location: Sweden, Växjö

Serial mouse

Post by Jaix »

Serila mouse shouldn't be any problem, I have tried a while ago (actually quite a while), and it should work.
There is one thing you should check though, it's the c:\freeldr.ini file, it can include a line (often in the end of the file) that enables bootlogging to COM1, this should be exchanged for SCREEN instead.

Code: Select all

Options=/DEBUGPORT=SCREEN
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

Cool! I didn't know that it's possible to redirect debug output from COM1 to Screen. I'll try it soon!
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

Actually I don't seem to get any debug messages on screen even if I try this setting in freeldr.
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

And what are valid values for Debugport directive?
GreyGhost
Posts: 295
Joined: Mon Jun 13, 2005 12:16 pm

Post by GreyGhost »

Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

Well, even if I set debugport directive DEBUGPORT=FILE it doesn't create debug.log file in reactos directory. So... no debug messages regardless of using =SCREEN or =FILE.

Installation has added another option to this line... it looks like this:
Options=/DEBUGPORT=FILE /NOGUIBOOT

Don't know why it is NOGUIBOOT by default, but GUI boots anyway.

Do I have to get a special debug build of ReactOS to get debug messages, or what is wrong??
WaxDragon
Developer
Posts: 28
Joined: Wed Dec 08, 2004 8:02 am

Post by WaxDragon »

Tiansen wrote:Well, even if I set debugport directive DEBUGPORT=FILE it doesn't create debug.log file in reactos directory. So... no debug messages regardless of using =SCREEN or =FILE.
Release builds output very little debug output. You will want to use a debug build to get more information. As for DEBUGPORT=file, I've never used it. I use COM1 or SCREEN.
Tiansen wrote:Installation has added another option to this line... it looks like this:
Options=/DEBUGPORT=FILE /NOGUIBOOT

Don't know why it is NOGUIBOOT by default, but GUI boots anyway.
NOGUIBOOT should really be called NOBOOTSPLASH. ;0) It just prevents the display of the blueish-grey ReactOS boot logo. On a fast machine it goes by so fast you hardly see it anyway.
Tiansen wrote:Do I have to get a special debug build of ReactOS to get debug messages, or what is wrong??
We even provided a debug build of RC1 on sourceforge. (Look for reactos0.3.0-RC1-DBG.zip).

As for a serial mouse, Others have cliamed it works, but it didn't when I tried it.

WD
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

Well, for me it's only possible to use serial or USB mouse. Serial doesn't work for me, ReactOS also doesn't support USB at the moment. So there's no mouse for me. :roll:

I'll try to install debug version of ROS.
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

Well, actually there are some quite interesting things in debug log as follows:

(./ntoskrnl/ke/main.c:291) ---------------------------------------------------------------
(./ntoskrnl/ke/main.c:292) ReactOS 0.3-RC1 (Build 20060618-r22375)
Used memory 65536Kb
(./ntoskrnl/mm/mminit.c:387) Kernel Stack Limits. InitTop = 0x800b3000, Init = 0x800b0000
(./ntoskrnl/mm/mm.c:283) No current process
(./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2096) Initialization of service serial failed (Status c0000001)
(./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\serial.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2096) Initialization of service serial failed (Status c0000001)
(./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pciidex.sys (Status 0xc0000001)
(./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\system32\pciidex.sys (Status 0xc0000001)
(./ntoskrnl/ldr/loader.c:1270) Unknown import module: pciidex.sys (Status c0000001)
(./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2096) Initialization of service pciide failed (Status c0000001)
(./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pciidex.sys (Status 0xc0000001)
(./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\system32\pciidex.sys (Status 0xc0000001)
(./ntoskrnl/ldr/loader.c:1270) Unknown import module: pciidex.sys (Status c0000001)
(./ntoskrnl/ldr/loader.c:267) Could not open module file: \SystemRoot\System32\drivers\pciide.sys (Status 0xc0000001)
(./ntoskrnl/io/pnpmgr.c:2096) Initialization of service pciide failed (Status c0000001)
(./ntoskrnl/io/driver.c:1295) Driver 'buslogic.sys' load failed, status (c0000001)
(./ntoskrnl/io/driver.c:1295) Driver 'atapi.sys' load failed, status (c0000035)
(./ntoskrnl/io/pnpreport.c:86) IoReportResourceForDetection partly implemented


There is a mention of failed serial.sys driver. I've checked and that file actually exists in ReactOS/system32/drivers directory (if SystemRoot equals /ReactOS?!?). I hope that ROS isn't case sensitive because in the log it says System32, but actually it is system32. Anybody knows why it cannot load some drivers according to log?

I hope that some developers know what's going wrong here...
And what means status 0xc0000001?
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

no ideas? :(
Coviti
Posts: 300
Joined: Wed Mar 01, 2006 4:26 am

Post by Coviti »

Tiansen, status 0xc0000001 simply is "STATUS_UNSUCCESSFUL", which means that the operation failed. It appears that ReactOS simply failed to load the drivers listed.
Tiansen
Posts: 39
Joined: Tue Apr 18, 2006 1:56 pm

Post by Tiansen »

Yes, and I think that serial.sys is driver for serial port or serial mouse and therefore my mouse doesn't work. Why it fails? Is it a bug or something?
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests