Reactos 0.3.11 possible on 430CDS Satellite Pro?

[arobbo]

Cheers ReactOS Team and Community,

I'm attempting the 3.1.1 Distro on a Toshiba SatellitePro 430CDS laptop but have video problems I can't find discussed elsewhere on the support forum.

With a full installation, on bootup I get a clear boot flash screen (looks great, can provide photos if requested) after which the screen garbles due to incorrect video settings. The appearance is blocky and gridded as if viewed through a rectangular Freznel lens - the projection is out-of-synch somehow, dialog boxes and mouse tracking is vauguely discernible. Not VESA2.0-compatible, I wonder?
I run Win98SE and various Linux distros fine on this machine with 800x600 x16 VESA. I thought I might find a solution in manually entering the codes needed, but can't even seem to get to a debug or command-prompt option that would permit this. Is ReactOS 0.3.11 possible on such a machine?

Any suggestions or advice gratefully received.
Thanks.

-----------TECHNICAL DETAILS----------------------
The specifications are:
48Mb Edo RAM, 120MHz Pentium CPU, PS/2 mouse

Video settings in XF86Config (excerpt):
Section "Monitor"
Identifier "Laptop Screen"
VendorName "Toshiba"
ModelName "DD-STN"
HorizSync 31.5-48.5 [HorizSync 31.5 - 43]
VertRefresh 40-75
# VESA 800x600@60Hz Non-Interlaced mode Horizontal Sync = 37.9kHz
Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
# VESA 640x480@72Hz Non-Interlaced mode Horizontal Sync = 37.9kHz
Modeline "640x480" 31.50 640 664 704 832 480 489 492 520
EndSection

Section "Device"
Identifier "Chips & Technologies CT65550"
VendorName "Chips & Technologies"
BoardName "CT65550"
EndSection

Section "Screen"
Driver "SVGA"
Device "Chips & Technologies CT65550"
Monitor "Laptop Screen"
BlankTime 2
SuspendTime 5
OffTime 10
DefaultColorDepth 16
SubSection "Display"
Depth 8
Modes "800x600"
ViewPort 0 0
EndSubSection
EndSection

I also get no startup sounds as I might from Win98. Is the soundcard supported by ReactOS? From XF86Config:
Chipsets
ESS Technologies ESS688 & Yamaha OPL3 (YMF262)

Sound formats supports
SoundBlaster Pro V3.01, .WAV, MIDI,
Zoomed video port audio (stereo),
CardBus audio (monaural), CD-ROM audio.

[Haos]

Could you paste somewhere a copy of that garbled screen you get? What option did you pick at setup? VESA or VGA?

First of all, there is no point in testing ROS on that machine if it doesn't have a serial port and you don't have another machine to record debug logs. Without it, there is no way in seeing what goes wrong. As for now, ReactOS shouldn't be used for anything bar testing. Its not stable enough for production use.

If this is due to our VESA driver issues, there are ways to circumvent it. My favorite one is to run XP on hardware you want to use for ROS, backup all drivers you require (i use Double Driver application for that), building my own ReactOS bootcd with those XP drivers slipstreamed into it.

As for sound support, you will need to provide the XP drivers when prompted.

[hto]

First of all, there is no point in testing ROS on that machine if it doesn't have a serial port

There is also logging into a file.

[Haos]

Tried that ages ago, before i got a null modem. It didn't work.

[hto]

Ages ago it was broken.

mouse tracking is vauguely discernible.

If the pointer moves, it is not a crash.

[arobbo]

Thankyou Haos and hto for your rapid replies.

I couldn't find how to post attachments on this forum so you're welcome to download them ("Toshiba 430CDS splash" and "Toshiba 430CDS scamble"). The 'scramble' I just assume is an aliasing effect from misfit resolution detection/selection - everything else appear working, with mouse movement, dialogue closure (via keyboard) etc. echoed on-screen

http://www.mediafire.com/i/?jlymnmnjmmy (Splash)

http://www.mediafire.com/i/?tvqww1ulqjn(Scramble).

Please let me know if you have problems with the download,

Thanks Again.

[arobbo]

P.S. Identical responses to both VESA and VGA selections and others via the F8 options.

Cheers.

[hto]

Try to select ReactOS (Log file) on boot. It will produce a file C:\ReactOS\debug.log

[arobbo]

Sorry that I was delayed in my reply.
I've replaced the IDE hard-drive, wiped and re-partitioned with FAT32 with Gparted, and after selecting VESA mode for installation, booted ReactOS with log file to get the file contents provided below. The machine has the latest bios version (6.50) with these additional details from the BIOS menu:- VGA-compatible display adapter (CT65550 chip); VGA segment address=E400H; 222K colors. The adapter is VESA2.0-compatible, according to mainboard utilities in UBCD 4.11.

Hope this sheds some light on the issue,
Thanks.


C:\ReactOS\debug.log contents:

(ntoskrnl\kd\kdio.c:171) ---------------------------------------------------------------
(ntoskrnl\kd\kdio.c:172) ReactOS 0.3.11 (Build 20091212-r44553)
PC Compatible Eisa/Isa HAL has been initialized
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMENTED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMENTED!
(ntoskrnl\io\iomgr\driver.c:1391) '\Driver\BUSLOGIC' initialization failed, status (0xc00000c0)
wood_uhci: Entering DriverEntry(), RegistryPath=
\Registry\Machine\System\CurrentControlSet\Services\usbdriver
(ntoskrnl\io\iomgr\driver.c:1391) '\Driver\usbdriver' initialization failed, status (0xc0000001)
(ntoskrnl\io\iomgr\file.c:420) Using IopParseDevice() hack. Requested invalid attributes: 1
(ntoskrnl\vdm\vdmmain.c:26) VME support detected but not yet taken advantage of
(subsystems\win32\win32k\ntuser\sysparams.c:1499) UserSystemParametersInfo called without active windowstation.
err:(dll\win32\user32\misc\dllmain.c:367) GetConnected
(subsystems\win32\win32k\ntuser\desktop.c:604) RtlQueryRegistryValues failed for PaintDesktopVersion (c0000034)
(subsystems\win32\win32k\ntuser\sysparams.c:1499) UserSystemParametersInfo called without active windowstation.
(subsystems\win32\win32k\objects\gdiobj.c:951) Attempted to lock object 0x0 of wrong type (Handle: 0x0, requested: 0x50000)
(subsystems\win32\win32k\objects\gdiobj.c:951) Attempted to lock object 0x0 of wrong type (Handle: 0x0, requested: 0x50000)
(subsystems\win32\win32k\objects\gdiobj.c:951) Attempted to lock object 0x0 of wrong type (Handle: 0x0, requested: 0x50000)
(subsystems\win32\win32k\objects\gdiobj.c:951) Attempted to lock object 0x0 of wrong type (Handle: 0x0, requested: 0x50000)
err:(dll\win32\user32\windows\window.c:292) CreateWindowExA RegisterSystemControls
(dll\ntdll\ldr\utils.c:2227) Relocating (74a30000 -> 00F70000) C:\ReactOS\System32\syssetup.dll
err:(dll\win32\iphlpapi\ifenum_reactos.c:101) openTcpFile for <\Device\Tcp> failed: 0xc0000034
err:(dll\win32\iphlpapi\ifenum_reactos.c:101) openTcpFile for <\Device\Tcp> failed: 0xc0000034
err:(dll\win32\iphlpapi\ifenum_reactos.c:101) openTcpFile for <\Device\Tcp> failed: 0xc0000034
err:(dll\win32\iphlpapi\ifenum_reactos.c:101) openTcpFile for <\Device\Tcp> failed: 0xc0000034
(base\services\umpnpmgr\umpnpmgr.c:2302) Unknown event, GUID {CB3A4009-46F0-11D0-B08F-00609713053F}
(base\services\umpnpmgr\umpnpmgr.c:2302) Unknown event, GUID {CB3A4009-46F0-11D0-B08F-00609713053F}
err:(dll\win32\iphlpapi\ifenum_reactos.c:101) openTcpFile for <\Device\Tcp> failed: 0xc0000034
err:(dll\win32\iphlpapi\ifenum_reactos.c:101) openTcpFile for <\Device\Tcp> failed: 0xc0000034
err:(dll\win32\shell32\shellpath.c:1468) Failed to create directory L"%USERPROFILE%\\Local Settings\\Temporary Internet Files".
err:(dll\win32\wininet\urlcache.c:554) Couldn't get path for default container 0
err:(dll\win32\shell32\shellpath.c:1468) Failed to create directory L"%USERPROFILE%\\Local Settings\\History".
err:(dll\win32\wininet\urlcache.c:554) Couldn't get path for default container 1
err:(dll\win32\shell32\shellpath.c:1468) Failed to create directory L"%USERPROFILE%\\Cookies".
err:(dll\win32\wininet\urlcache.c:554) Couldn't get path for default container 2
(dll\ntdll\ldr\utils.c:2227) Relocating (74a30000 -> 01130000) C:\ReactOS\system32\syssetup.dll
(dll\ntdll\ldr\utils.c:2227) Relocating (74a30000 -> 01130000) C:\ReactOS\system32\syssetup.dll
(dll\ntdll\ldr\utils.c:2227) Relocating (74a30000 -> 01130000) C:\ReactOS\system32\syssetup.dll
(dll\ntdll\ldr\utils.c:2227) Relocating (74a30000 -> 01130000) C:\ReactOS\system32\syssetup.dll
err:(dll\win32\setupapi\queue.c:1659) copy error 2 L"C:\\ReactOS\\inf\\i8042prt.sys" -> L"C:\\ReactOS\\System32\\drivers\\i8042prt.sys"
err:(dll\win32\setupapi\queue.c:1659) copy error 2 L"C:\\ReactOS\\inf\\mouclass.sys" -> L"C:\\ReactOS\\System32\\drivers\\mouclass.sys"
(dll\ntdll\ldr\utils.c:2227) Relocating (74a30000 -> 01130000) C:\ReactOS\system32\syssetup.dll
(dll\ntdll\ldr\utils.c:2227) Relocating (74a30000 -> 01130000) C:\ReactOS\system32\syssetup.dll

[Haos]

Nothing wrong in that log.

[arobbo]

Thanks for translating that for me, Haos - it's all completely gibberish to a newbie like myself.

OK- some other observations that I have made on a few more attempts at installing ReactOS:

1. Repartitioned the drive (another HD to the one used previously) using fdisk, fdisk /mbr, and format options via Win98 installation floppy and disc. Single FAT32 partition as advised in installation dialogues. Reinstall 'borks' at same point shown in the 'scramble' shot provided earlier.
2. Ditto point 1 above for repartitioning, reformatting to FAT32 (either full or quick, or "Keep current format") via the Reactos installation options.
3. In the final installation dialogue (after "Remove floppy and CD and press a key", I think) - I cannot read the message starting with "ReactOS will now... may take a few minutes" - as the machine reboots almost immediately at this point. A clue?
4. I've only really attempted installing Freeloader to the HD bootsector. Thinking that this might be related to the problem, I have also installed with "Don't install Freeloader" (or bootloader) and then installed GAG 4.10 - I get a "freeldr.sys not found" message, and naturally also if booting from a floppy Grub4Dos. No resolution there, but unlikely because -
5. I get the same scramble if booting from LiveCD ReactOS 3.11.
6. I note that during the full installation procedure, the blue backgrounded setup dialogues do not take the entire screen, but compress to a page the same width as the broad band seen in the "scramble" jpg provided earlier (although readable and positioned more central to the screen). Is this typical? The screen compression occurs despite "Text Mode Stretch = Enabled" being selected in the BIOS.
7. I can't soft-boot from the scrambled screen: Ctrl-Alt-Del, Ctrl-Alt-Bksp return no visible reaction. Alt-F4 seems to close something down however, but I can't resume from that point without a hard reset.

8. Might there be some sort of conflict relating to PCI or ACPI detection (the 430cds has none - I use "apm=on" if using Puppy Linux on these machines)?
9. Your "Recovery Console" option in the installation menus drops the user back to the main installation menu.

I think that that about covers my experiments. I'll have to say "Adios, ReactOS" now for the time being but I will watch with great interest developments for old Toshiba Laptops,

Thanks, ReactOS Team

[wojo664]

ACPI detection

ACPI is not enabled yet in trunk (i think)