Real hardware 0.4.9

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

swight
Posts: 130
Joined: Thu Jan 10, 2008 10:31 pm

Real hardware 0.4.9

Post by swight »

Did some minimal testing of 0.4.9 on a hand me down pc I got from a relative. currently do not have a hard drive for it since relative wanted to keep data on old hard drive so used live cd version.

The computer was an HP Pavilion Slimline which has a amd sempron processor and originally had windows vista.hopefully that will let someone track down more exact model.

Initial tests ReactOS did not successfully boot at all. Eventually tracked down the problem. in order to fix the problem I needed to disconnect the front USB ports from the motherboard. once this was removed Reactos Booted successfully to desktop.

Successfully used Dell RT7D20 and Microsoft Wireless Keyboard 6000 v3.0 keyboards with a side note if any usb device was added or removed from the systems after the system was fully booted to desktop both keyboards stopped functioning til reboot. usb devices plugged in before booting up did not cause problems til they were removed.

The hardware that prevented Reactos from booting was HP Pin:505183-001 SN:Nw92406071 just unplugging the usb connector to it at the motherboard solved the issue without having to unplug anything else.

may do some proper bug reports later. No network tests were done(largely because no wired network available in room with that computer and I don't know what commands I would need for wifi to activate it with keyboard only.) this was a pure does it boot and does basic input work test. I was unable to find a mouse atm that would work. Microsoft Wireless Mobile Mouse 3500 I had lying around did not work.

Julcar
Posts: 129
Joined: Thu Jul 31, 2008 8:19 pm

Re: Real hardware 0.4.9

Post by Julcar »

PS/2 keyboards and mice are supposed to work out of the box, with usb the scenario changes because you would need to compile yourself with some patches available on the wiki to get some usb features working.

SoupBowl
Posts: 11
Joined: Thu Jul 26, 2018 5:30 am

Re: Real hardware 0.4.9

Post by SoupBowl »

Julcar wrote:
Sun Jul 29, 2018 2:31 am
PS/2 keyboards and mice are supposed to work out of the box
Been looking at some Motherboards Pico-ITX/Mini-ITX and i have noticed a few that have only 1 PS/2 port(if any)
they appear to have this port designed to work with either keyboard or mouse, besides making us chose between a keyboard or mouse.

sometimes they have serial ports as tiny PC's have niche uses in mind, would this be good for a mouse under react os? i have an old RS232 mouse
swight wrote:
Sat Jul 28, 2018 11:25 pm
in order to fix the problem I needed to disconnect the front USB ports from the motherboard. once this was removed Reactos Booted successfully to desktop.
Might be best for me to Wait until React OS 0.5.0 but im planning to piece together a portable computer designed to run off a 12 volt leisure battery and thought it might be fun to try react OS so just putting my question on keyboards and mouse here.

Julcar
Posts: 129
Joined: Thu Jul 31, 2008 8:19 pm

Re: Real hardware 0.4.9

Post by Julcar »

AFAIK Reactos reserves the serial port a.k.a COM1 for debugging tasks, so the serial mouse probably won't work.

you could better see if your mother boards uses usb 1.1, because the UHCI driver has some more stability than EHIC and OHCI

SoupBowl
Posts: 11
Joined: Thu Jul 26, 2018 5:30 am

Re: Real hardware 0.4.9

Post by SoupBowl »

Haven't decided on the board i want to buy yet but they will probably have USB 2.0/3.0 being new devices
i don't know if there is any way to trick React OS into believing they are 1.1, probably not?
Julcar wrote:
Sun Jul 29, 2018 3:31 am
AFAIK Reactos reserves the serial port a.k.a COM1 for debugging tasks, so the serial mouse probably won't work.

you could better see if your mother boards uses usb 1.1, because the UHCI driver has some more stability than EHIC and OHCI
Interesting observations on the USB and serial issues will keep in mind

In the meantime
I do have an old laptop similar to what sight has mentions same era different manufacturer, just need to find the charger.
Once ive picked up some blank disks to burn ReactOS-0.4.9-Live.iso(Hopefully i don't forget the drivers specific to the laptop) and try it with non wireless keyboard and mouse i might hopefully have something to add to this.

Might see something might get nothing of note but i will give it a whirl!

P.S.
Unrelated question
Any recommendations on browsers, been trying K-Meleon 77 seems to work ok but doesn't have full HTML5 support so will not work on Vimeo and certain parts of YouTube.
is there a browser that will handle these on React OS or a trick to get these to work?

Julcar
Posts: 129
Joined: Thu Jul 31, 2008 8:19 pm

Re: Real hardware 0.4.9

Post by Julcar »

SoupBowl wrote:
Sun Jul 29, 2018 5:24 am
Haven't decided on the board i want to buy yet but they will probably have USB 2.0/3.0 being new devices
i don't know if there is any way to trick React OS into believing they are 1.1, probably not?
Julcar wrote:
Sun Jul 29, 2018 3:31 am
AFAIK Reactos reserves the serial port a.k.a COM1 for debugging tasks, so the serial mouse probably won't work.

you could better see if your mother boards uses usb 1.1, because the UHCI driver has some more stability than EHIC and OHCI
Interesting observations on the USB and serial issues will keep in mind

In the meantime
I do have an old laptop similar to what sight has mentions same era different manufacturer, just need to find the charger.
Once ive picked up some blank disks to burn ReactOS-0.4.9-Live.iso(Hopefully i don't forget the drivers specific to the laptop) and try it with non wireless keyboard and mouse i might hopefully have something to add to this.

Might see something might get nothing of note but i will give it a whirl!

P.S.
Unrelated question
Any recommendations on browsers, been trying K-Meleon 77 seems to work ok but doesn't have full HTML5 support so will not work on Vimeo and certain parts of YouTube.
is there a browser that will handle these on React OS or a trick to get these to work?
You can know the usb driver your mother board is using by seeing the debug log to text file mode, as it is dumped at boot time.

about the web browser, you could try Midori

User avatar
dizt3mp3r
Posts: 1596
Joined: Mon Jun 14, 2010 5:54 pm

Re: Real hardware 0.4.9

Post by dizt3mp3r »

There is a palemoon build for XP that should be able to run (untested). There are builds of all the main browsers that ought to work too, just go for an older build.
Skillset: VMS sysadmin 20 years, fault Tolerance, cluster, Vax, Alpha, ftSparc. DCL, QB45, VB6, NET, PHP, JS, CMS, Graphics, Project Manager, DOS, Windows admin from 1985. Quad Electronics. Classic cars & motorbikes. Artist watercolours. Historian.

SoupBowl
Posts: 11
Joined: Thu Jul 26, 2018 5:30 am

Re: Real hardware 0.4.9

Post by SoupBowl »

Julcar wrote:
Sun Jul 29, 2018 10:16 am
You can know the usb driver your mother board is using by seeing the debug log to text file mode, as it is dumped at boot time.
will keep in mind when testing things out
Julcar wrote:
Sun Jul 29, 2018 10:16 am
about the web browser, you could try Midori
Haven't quite got it to run yet will probably figure it out soon,
considering many apps need workarounds and tweaks i think it would be a good idea for us to document these considering that with few exceptions the web browser is the app that changes the most per update.
dizt3mp3r wrote:
Sun Jul 29, 2018 12:47 pm
There is a palemoon build for XP that should be able to run (untested). There are builds of all the main browsers that ought to work too, just go for an older build.
will have a go with that soon

There are a handful of browsers that work, others don’t and others that will only work if a specific version is used.
Perhaps we could use a page like this for browsers and their performance on React OS
https://en.wikipedia.org/wiki/Compariso ... b_browsers
and keep a list of those that have worked but recently broke compatibility.

This page exists
https://reactos.org/wiki/Games_ROS_Testing

I will be playing with a few browsers so i could record my results and create such a page
https://reactos.org/wiki/Compatability_of_web_browsers
Unless there is already something similar I haven’t found yet.

Julcar
Posts: 129
Joined: Thu Jul 31, 2008 8:19 pm

Re: Real hardware 0.4.9

Post by Julcar »

To be honest, I preffer use portable web browsers, Kmeleon sadly got outdated, so I am using QtWeb, which is outdated too :lol: but at leaset have a lot of webkit features about html5 and javascript

SoupBowl
Posts: 11
Joined: Thu Jul 26, 2018 5:30 am

Re: Real hardware 0.4.9

Post by SoupBowl »

Julcar wrote:
Mon Jul 30, 2018 3:48 am
To be honest, I preffer use portable web browsers, Kmeleon sadly got outdated, so I am using QtWeb, which is outdated too :lol: but at leaset have a lot of webkit features about html5 and javascript
There was a new release a few months ago 2018 (K-Meleon 77)
Seems to run fine on React Os, Got Blue screens a few times on Windows 2000 but that was only a few specific things that seems to trigger it but did not experience this under React OS.
My point is "What Browser do i use?" is not a straightforward question.
So i think next time i have some free time i will run maybe 3 - 5 browsers do some tests and whip up a page comparing them
Have a chart like this
https://en.wikipedia.org/wiki/Compariso ... nformation
But rather than
Browser, Creator, Cost, License, Layout engine, Latest release

Browser, Stability, Noteworthy Feature, Latest release, Latest working release
and a chart like this to show what features work(Specifically under react os)
https://en.wikipedia.org/wiki/Compariso ... r_features
HTML5 has a ton of optional features so that should be broken up into several categories on the features chart as to say "its HTML 5 comparable" is so nonspecific its almost meaningless.

Getting off topic so i will come back later and bump this when ive tried React Os on a laptop (unless it does nothing)

So i will start a browser related thread when i have something to add and hopefully get some suggestions to make that Wiki page

qbancoffee
Posts: 10
Joined: Mon Aug 06, 2018 5:44 pm

Re: Real hardware 0.4.9

Post by qbancoffee »

This thread got me interested in trying ReactOS on real hardware, good to see it's installing on other computers.

I was planning on throwing away two older computers I've had collecting dust for some time when I thought "hey, maybe I can
do some ReactOS testing". For testing I used:
ReactOS 0.4.9 (Build 20180712-0.4.9-release-0-ga920a96) (Commit a920a9672c5768c66714789a52af0a8255cb5161)

The first test computer is a Dell inspiron 6000 with a celeron m processor. The results were nice. ReactOS installed without issue but getting
the lan driver to install took some work. I manually copied driver files to the correct directory in order to get it to work.
After that, things ran as expected. I was even able to use openjdk 8 to compile and run several java programs.

The second test computer is a Dell optiplex gx270.
ReactOS installed but did not boot all the way. This computer has a real serial port so made a null modem cable
and captured the debug output on a separate computer.

Below is the Debug capture.

Code: Select all

(../../ntoskrnl/kd/kdio.c:104) -----------------------------------------------------
(../../ntoskrnl/kd/kdio.c:105) ReactOS 0.4.9 (Build 20180712-0.4.9-release-0-ga920a96) (Commit a920a9672c5768c66714789a52af0a8255cb5161)
(../../ntoskrnl/kd/kdio.c:106) 1 System Processor [2046 MB Memory]
(../../ntoskrnl/kd/kdio.c:107) Command Line: DEBUG DEBUGPORT=COM1 BAUDRATE=115200 SOS
(../../ntoskrnl/kd/kdio.c:108) ARC Paths: multi(0)disk(0)rdisk(0)partition(1) \ multi(0)disk(0)rdisk(0)partition(1) \WINDOWS\
(../../ntoskrnl/ke/i386/cpu.c:450) Supported CPU features : KF_V86_VIS KF_RDTSC KF_CR4 KF_CMOV KF_GLOBAL_PAGE KF_LARGE_PAGE KF_MTRR KF_CMPXCHG8B KF_MMX KF_WORKING_PTE KF_PAT KF_FXSR KF_FAST_SYSCALL KF_XMMI   KF_XMMI64 KF_DTS   
(../../ntoskrnl/ke/i386/cpu.c:722) Prefetch Cache: 64 bytes\0x09L2 Cache: 524288 bytes\0x09L2 Cache Line: 64 bytes\0x09L2 Cache Associativity: 8
(../../hal/halx86/acpi/halacpi.c:782) ACPI Timer at: 808h (EXT: 0)
(../../hal/halx86/acpi/halacpi.c:533) ACPI Boot table found, but not supported!
(../../hal/halx86/acpi/halacpi.c:890) ACPI 2.0 Detected. Tables: [RSDT] [FACP] [BOOT] 
(../../ntoskrnl/mm/ARM3/mminit.c:1452) HAL I/O Mapping at FFFE0000 is unsafe
(../../ntoskrnl/mm/mminit.c:131)           0x80000000 - 0x83400000\0x09Boot Loaded Image
(../../ntoskrnl/mm/mminit.c:135)           0xB0000000 - 0xB0DFE000\0x09PFN Database
(../../ntoskrnl/mm/mminit.c:139)           0xB0DFE000 - 0xB4DB6000\0x09ARM3 Non Paged Pool
(../../ntoskrnl/mm/mminit.c:143)           0xB9400000 - 0xBB400000\0x09System View Space
(../../ntoskrnl/mm/mminit.c:147)           0xBB400000 - 0xC0000000\0x09Session Space
(../../ntoskrnl/mm/mminit.c:150)           0xC0000000 - 0xC03FFFFF\0x09Page Tables
(../../ntoskrnl/mm/mminit.c:153)           0xC0300000 - 0xC0300FFF\0x09Page Directories
(../../ntoskrnl/mm/mminit.c:156)           0xC0400000 - 0xC07FFFFF\0x09Hyperspace
(../../ntoskrnl/mm/mminit.c:159)           0xC1000000 - 0xE0FFFFFF\0x09System Cache
(../../ntoskrnl/mm/mminit.c:163)           0xE1000000 - 0xECC00000\0x09ARM3 Paged Pool
(../../ntoskrnl/mm/mminit.c:166)           0xECC00000 - 0xF7BE0000\0x09System PTE Space
(../../ntoskrnl/mm/mminit.c:169)           0xF7BE0000 - 0xFFBE0000\0x09Non Paged Pool Expansion PTE Space
(../../ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB4D55008, 2) is UNIMPLEMENTED!
ACPI Compatible Eisa/Isa HAL Detected
(../../sdk/lib/rtl/image.c:171) Invalid base address: 00000000
(../../ntoskrnl/io/iomgr/driver.c:1585) '\Driver\SACDRV' initialization failed, status (0xc0000037)
(../../ntoskrnl/io/iomgr/driver.c:64) Deleting driver object '\Driver\SACDRV'
(../../drivers/storage/scsiport/scsiport.c:5859) ZwOpenKey() failed with Status=0xC0000034
(../../hal/halx86/legacy/bus/pcibus.c:727) WARNING: PCI Slot Resource Assignment is FOOBAR
(../../ntoskrnl/io/iomgr/iorsrce.c:874) IoReportResourceUsage is halfplemented!
(../../ntoskrnl/io/iomgr/iorsrce.c:874) IoReportResourceUsage is halfplemented!
(../../hal/halx86/legacy/bus/pcibus.c:727) WARNING: PCI Slot Resource Assignment is FOOBAR
(../../ntoskrnl/io/iomgr/driver.c:1585) '\Driver\BUSLOGIC' initialization failed, status (0xc00000c0)
(../../ntoskrnl/io/iomgr/driver.c:64) Deleting driver object '\Driver\BUSLOGIC'
(../../drivers/filesystems/fastfat/iface.c:145) FastFAT KDBG extension registered: yes
(../../drivers/ksfilter/swenum/swenum.c:428) SWENUM loaded
(../../drivers/bus/acpi/buspdo.c:833) Failed to find a bus number
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:2817) IopStartDevice(ACPI\FixedButton\2&ccb86d17&0) failed with status 0xc0000005
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:2817) IopStartDevice(ACPI\GenuineIntel_-_x86_Family_15_Model_2\_0) failed with status 0xc0000005
(../../ntoskrnl/io/pnpmgr/pnpmgr.c:2817) IopStartDevice(ACPI\GenuineIntel_-_x86_Family_15_Model_2\_1) failed with status 0xc0000005
(../../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\System32\DRIVERS\i8042prt.sys' with status 0xc000003a
(../../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\system32\drivers\vbemp.sys' with status 0xc000003a
(../../ntoskrnl/mm/ARM3/sysldr.c:3025) ZwOpenFile failed for '\SystemRoot\System32\DRIVERS\i8042prt.sys' with status 0xc000003a
(../../ntoskrnl/io/iomgr/iorsrce.c:725) Failed to open symlink \Device\Harddisk0\Partition1, Status=c0000024
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\vbemp.sys at F7759000 with c pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\videoprt.sys at F7733000 with 26 pages
(../../ntoskrnl/io/pnpmgr/pnpinit.c:325) IopOpenRegistryKeyEx() failed for '{4D36E968-E325-11CE-BFC1-08002BE10318}' with status 0xc0000034
WARNING:  ExUuidCreate at ../../ntoskrnl/ex/uuid.c:305 is UNIMPLEMENTED!
(../../win32ss/drivers/videoprt/registry.c:312) Failed to open device software key. Status 0xc0000034
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\DRIVERS\i8042prt.sys at F7718000 with 1b pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\kbdclass.sys at F7704000 with 14 pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\floppy.sys at F76EB000 with 19 pages
(../../ntoskrnl/io/iomgr/driver.c:1585) '\Driver\FLOPPY' initialization failed, status (0xc000000e)
(../../ntoskrnl/io/iomgr/driver.c:64) Deleting driver object '\Driver\FLOPPY'
(../../ntoskrnl/io/iomgr/driver.c:1995) IopInitializeDriverModule() failed (Status c000000e)
(../../ntoskrnl/mm/ARM3/sysldr.c:955) Leaking driver: floppy.sys
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\cdrom.sys at F76CC000 with 1b pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\fs_rec.sys at F76BE000 with e pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\null.sys at F76B5000 with 9 pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\beep.sys at F76AC000 with 9 pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\mouclass.sys at F769E000 with e pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\blue.sys at F7693000 with b pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\msfs.sys at F7688000 with b pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\npfs.sys at F7666000 with 22 pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\ndisuio.sys at F7657000 with f pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\afd.sys at F7628000 with 2f pages
WARNING:  RtlCreateTagHeap at ../../sdk/lib/rtl/heap.c:3881 is UNIMPLEMENTED!
(../../base/system/autochk/autochk.c:311) AUTOCHK: Checking \??\C:
(../../drivers/filesystems/fastfat/fsctl.c:1212) HACK: Using lock-hack!
(../../base/system/smss/pagefile.c:878) SMSS:PFILE: Open volume `\??\D:\' failed with status C000014F
Boot took 17275244036 cycles!
Interrupts: 901 System Calls: 17116 Context Switches: 652
(../../ntoskrnl/config/cmsysini.c:1238) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1238) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1238) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1238) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1238) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1238) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmsysini.c:1238) CmpGetRegistryPath: ConfigPath = '\SystemRoot\System32\Config\'
(../../ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB496A3E8, 0) is UNIMPLEMENTED!
(../../ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB4969008, 0) is UNIMPLEMENTED!
(../../ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB497F370, 0) is UNIMPLEMENTED!
(../../ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB497D008, 0) is UNIMPLEMENTED!
(../../ntoskrnl/mm/ARM3/session.c:790) Session 0 is ready to go: 0xBF7F0000 0xF75FC000, 7f6d2 0xB496B008
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\win32k.sys at F7331000 with 2b3 pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\ftfd.dll at F71FE000 with 133 pages
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\framebuf.dll at F71F1000 with d pages
(../../win32ss/user/ntuser/class.c:2335) err: SYSTEMCUR(ARROW) == NULL, should not happen!!
(../../win32ss/user/ntuser/class.c:2335) err: SYSTEMCUR(ARROW) == NULL, should not happen!!
(../../win32ss/user/ntuser/class.c:2335) err: SYSTEMCUR(ARROW) == NULL, should not happen!!
(../../win32ss/user/ntuser/class.c:2335) err: SYSTEMCUR(ARROW) == NULL, should not happen!!
(../../win32ss/user/ntuser/class.c:2335) err: SYSTEMCUR(ARROW) == NULL, should not happen!!
(../../win32ss/user/ntuser/class.c:2335) err: SYSTEMCUR(ARROW) == NULL, should not happen!!
(../../win32ss/user/ntuser/winsta.c:226) err: Invalid window station handle
(../../win32ss/user/ntuser/clipboard.c:31) err: Cannot open winsta
(../../win32ss/user/ntuser/winsta.c:494) err: Initializing input window station
(../../win32ss/user/ntuser/desktop.c:2513) err: Attempted to change thread desktop although the thread has windows!
(../../ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\System32\kbdus.dll at F71CC000 with 5 pages
(../../base/system/services/services.c:279) ScmApplyServiceAccountsHack()
(../../base/system/services/services.c:148) ScmLogAccountsHack(LocalService, S-1-5-19)
(../../dll/win32/kernel32/client/loader.c:384) LoadLibraryExW(wlnotify.dll) failing with status c0000135
(../../dll/win32/userenv/profile.c:351) Error: 2
(../../base/system/services/services.c:178) CreateUserProfileW() failed (error 2)
(../../base/system/services/services.c:241) ScmLogAccountsHack(LocalService) returned failure
(../../base/system/services/services.c:262) ScmCleanupServiceAccountsHack()
(../../dll/win32/userenv/profile.c:638) Error: 2
(../../dll/win32/userenv/profile.c:771) Error: 2
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
err:(../../win32ss/user/user32/windows/cursoricon.c:25) Loading System Cursors
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
err:(../../win32ss/user/user32/misc/dllmain.c:600) hIconSmWindows 00020060 hIconWindows 0002005E 
(../../win32ss/user/ntuser/callback.c:1138) err: hIconSmWindows 00020060 hIconWindows 0002005E 
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!
(../../win32ss/user/ntuser/desktop.c:2513) err: Attempted to change thread desktop although the thread has windows!
(../../base/system/services/services.c:64) ScmLogEvent: RegisterEventSourceW failed 1722
(../../dll/win32/userenv/profile.c:638) Error: 2
(../../dll/win32/userenv/profile.c:771) Error: 2
VBEMP: VBESetCurrentMode failed (14f)
(../../win32ss/gdi/eng/pdevobj.c:245) Failed to create PDEV surface!

*** Assertion failed: ppdev->pSurface != NULL
***   Source File: ../../win32ss/gdi/eng/mouse.c, line 52

Break repeatedly, break Once, Ignore, terminate Process or terminate Thread (boipt)? 
kdb:> 
To get detailed information on the gx270, I booted it with lubuntu 18.04 32 bit and ran several commands.

lshw

Code: Select all

lubuntu
    description: Desktop Computer
    product: OptiPlex GX270
    vendor: Dell Computer Corporation
    serial: 56FR751
    width: 32 bits
    capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp
    configuration: administrator_password=disabled boot=normal chassis=desktop cpus=1 power-on_password=disabled uuid=44454C4C-3600-1046-8052-B5C04F373531
  *-core
       description: Motherboard
       product: 0U1324
       vendor: Dell Computer Corp.
       physical id: 0
       serial: ..CN1374046306AD.
     *-firmware
          description: BIOS
          vendor: Dell Computer Corporation
          physical id: 0
          version: A07
          date: 06/26/2006
          size: 64KiB
          capacity: 448KiB
          capabilities: pci pnp apm upgrade shadowing escd cdboot bootselect edd int13floppytoshiba int5printscreen int9keyboard int14serial int17printer acpi usb agp ls120boot biosbootspecification netboot
     *-cpu
          description: CPU
          product: Intel(R) Pentium(R) 4 CPU 2.66GHz
          vendor: Intel Corp.
          physical id: 400
          bus info: cpu@0
          version: 15.2.7
          slot: Microprocessor
          size: 2666MHz
          capacity: 3600MHz
          width: 32 bits
          clock: 533MHz
          capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cpuid cid xtpr
          configuration: id=0
        *-cache:0
             description: L1 cache
             physical id: 700
             size: 8KiB
             capacity: 16KiB
             capabilities: internal write-back data
             configuration: level=1
        *-cache:1
             description: L2 cache
             physical id: 701
             size: 512KiB
             capacity: 512KiB
             capabilities: internal varies unified
             configuration: level=2
     *-memory
          description: System Memory
          physical id: 1000
          slot: System board or motherboard
          size: 2GiB
        *-bank:0
             description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
             physical id: 0
             slot: DIMM_1
             size: 512MiB
             width: 64 bits
             clock: 333MHz (3.0ns)
        *-bank:1
             description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
             physical id: 1
             slot: DIMM_2
             size: 512MiB
             width: 64 bits
             clock: 333MHz (3.0ns)
        *-bank:2
             description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
             physical id: 2
             slot: DIMM_3
             size: 512MiB
             width: 64 bits
             clock: 333MHz (3.0ns)
        *-bank:3
             description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
             physical id: 3
             slot: DIMM_4
             size: 512MiB
             width: 64 bits
             clock: 333MHz (3.0ns)
     *-pci
          description: Host bridge
          product: 82865G/PE/P DRAM Controller/Host-Hub Interface
          vendor: Intel Corporation
          physical id: 100
          bus info: pci@0000:00:00.0
          version: 02
          width: 32 bits
          clock: 33MHz
          configuration: driver=agpgart-intel
          resources: irq:0 memory:f8000000-f9ffffff
        *-display
             description: VGA compatible controller
             product: 82865G Integrated Graphics Controller
             vendor: Intel Corporation
             physical id: 2
             bus info: pci@0000:00:02.0
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: pm vga_controller bus_master cap_list rom
             configuration: driver=i915 latency=0
             resources: irq:16 memory:f0000000-f7ffffff memory:feb80000-febfffff ioport:ed98(size=8) memory:c0000-dffff
        *-generic UNCLAIMED
             description: System peripheral
             product: 82865G/PE/P Processor to I/O Memory Interface
             vendor: Intel Corporation
             physical id: 6
             bus info: pci@0000:00:06.0
             version: 02
             width: 32 bits
             clock: 33MHz
             configuration: latency=0
             resources: memory:80000000-80000fff
        *-usb:0
             description: USB controller
             product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1
             vendor: Intel Corporation
             physical id: 1d
             bus info: pci@0000:00:1d.0
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: uhci bus_master
             configuration: driver=uhci_hcd latency=0
             resources: irq:16 ioport:ff80(size=32)
           *-usbhost
                product: UHCI Host Controller
                vendor: Linux 4.15.0-20-generic uhci_hcd
                physical id: 1
                bus info: usb@2
                logical name: usb2
                version: 4.15
                capabilities: usb-1.10
                configuration: driver=hub slots=2 speed=12Mbit/s
        *-usb:1
             description: USB controller
             product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2
             vendor: Intel Corporation
             physical id: 1d.1
             bus info: pci@0000:00:1d.1
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: uhci bus_master
             configuration: driver=uhci_hcd latency=0
             resources: irq:19 ioport:ff60(size=32)
           *-usbhost
                product: UHCI Host Controller
                vendor: Linux 4.15.0-20-generic uhci_hcd
                physical id: 1
                bus info: usb@3
                logical name: usb3
                version: 4.15
                capabilities: usb-1.10
                configuration: driver=hub slots=2 speed=12Mbit/s
        *-usb:2
             description: USB controller
             product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3
             vendor: Intel Corporation
             physical id: 1d.2
             bus info: pci@0000:00:1d.2
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: uhci bus_master
             configuration: driver=uhci_hcd latency=0
             resources: irq:18 ioport:ff40(size=32)
           *-usbhost
                product: UHCI Host Controller
                vendor: Linux 4.15.0-20-generic uhci_hcd
                physical id: 1
                bus info: usb@4
                logical name: usb4
                version: 4.15
                capabilities: usb-1.10
                configuration: driver=hub slots=2 speed=12Mbit/s
        *-usb:3
             description: USB controller
             product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4
             vendor: Intel Corporation
             physical id: 1d.3
             bus info: pci@0000:00:1d.3
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: uhci bus_master
             configuration: driver=uhci_hcd latency=0
             resources: irq:16 ioport:ff20(size=32)
           *-usbhost
                product: UHCI Host Controller
                vendor: Linux 4.15.0-20-generic uhci_hcd
                physical id: 1
                bus info: usb@5
                logical name: usb5
                version: 4.15
                capabilities: usb-1.10
                configuration: driver=hub slots=2 speed=12Mbit/s
        *-usb:4
             description: USB controller
             product: 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller
             vendor: Intel Corporation
             physical id: 1d.7
             bus info: pci@0000:00:1d.7
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: pm debug ehci bus_master cap_list
             configuration: driver=ehci-pci latency=0
             resources: irq:23 memory:80001000-800013ff
           *-usbhost
                product: EHCI Host Controller
                vendor: Linux 4.15.0-20-generic ehci_hcd
                physical id: 1
                bus info: usb@1
                logical name: usb1
                version: 4.15
                capabilities: usb-2.00
                configuration: driver=hub slots=8 speed=480Mbit/s
              *-usb
                   description: Mass storage device
                   product: Cruzer Glide
                   vendor: SanDisk
                   physical id: 7
                   bus info: usb@1:7
                   logical name: scsi4
                   version: 1.00
                   serial: 4C531001410724114150
                   capabilities: usb-2.10 scsi emulated scsi-host
                   configuration: driver=usb-storage maxpower=224mA speed=480Mbit/s
                 *-disk
                      description: SCSI Disk
                      product: Cruzer Glide
                      vendor: SanDisk
                      physical id: 0.0.0
                      bus info: scsi@4:0.0.0
                      logical name: /dev/sdb
                      logical name: /cdrom
                      version: 1.00
                      serial: 4C531001410724114150
                      size: 29GiB (31GB)
                      capabilities: removable
                      configuration: ansiversion=6 logicalsectorsize=512 mount.fstype=iso9660 mount.options=ro,noatime,nojoliet,check=s,map=n,blocksize=2048 sectorsize=512 state=mounted
                    *-medium
                         physical id: 0
                         logical name: /dev/sdb
                         logical name: /cdrom
                         size: 29GiB (31GB)
                         capabilities: partitioned partitioned:dos
                         configuration: mount.fstype=iso9660 mount.options=ro,noatime,nojoliet,check=s,map=n,blocksize=2048 signature=16defdd1 state=mounted
                       *-volume
                            description: Hidden HPFS/NTFS partition
                            physical id: 1
                            logical name: /dev/sdb1
                            capacity: 1031MiB
                            capabilities: primary bootable hidden
        *-pci
             description: PCI bridge
             product: 82801 PCI Bridge
             vendor: Intel Corporation
             physical id: 1e
             bus info: pci@0000:00:1e.0
             version: c2
             width: 32 bits
             clock: 33MHz
             capabilities: pci normal_decode bus_master
             resources: ioport:d000(size=4096) memory:fea00000-feafffff
           *-network
                description: Ethernet interface
                product: 82540EM Gigabit Ethernet Controller
                vendor: Intel Corporation
                physical id: c
                bus info: pci@0000:01:0c.0
                logical name: enp1s12
                version: 02
                serial: 00:0f:1f:7d:4f:3d
                capacity: 1Gbit/s
                width: 32 bits
                clock: 66MHz
                capabilities: pm pcix msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
                configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.21-k8-NAPI latency=64 link=no mingnt=255 multicast=yes port=twisted pair
                resources: irq:18 memory:feae0000-feafffff ioport:df40(size=64)
        *-isa
             description: ISA bridge
             product: 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge
             vendor: Intel Corporation
             physical id: 1f
             bus info: pci@0000:00:1f.0
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: isa bus_master
             configuration: driver=lpc_ich latency=0
             resources: irq:0
        *-ide:0
             description: IDE interface
             product: 82801EB/ER (ICH5/ICH5R) IDE Controller
             vendor: Intel Corporation
             physical id: 1f.1
             bus info: pci@0000:00:1f.1
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: ide bus_master
             configuration: driver=ata_piix latency=0
             resources: irq:18 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:ffa0(size=16) memory:feb7fc00-feb7ffff
        *-ide:1
             description: IDE interface
             product: 82801EB (ICH5) SATA Controller
             vendor: Intel Corporation
             physical id: 1f.2
             bus info: pci@0000:00:1f.2
             version: 02
             width: 32 bits
             clock: 66MHz
             capabilities: ide bus_master
             configuration: driver=ata_piix latency=0
             resources: irq:18 ioport:fe00(size=8) ioport:fe10(size=4) ioport:fe20(size=8) ioport:fe30(size=4) ioport:fea0(size=16)
        *-serial UNCLAIMED
             description: SMBus
             product: 82801EB/ER (ICH5/ICH5R) SMBus Controller
             vendor: Intel Corporation
             physical id: 1f.3
             bus info: pci@0000:00:1f.3
             version: 02
             width: 32 bits
             clock: 33MHz
             configuration: latency=0
             resources: ioport:eda0(size=32)
        *-multimedia
             description: Multimedia audio controller
             product: 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller
             vendor: Intel Corporation
             physical id: 1f.5
             bus info: pci@0000:00:1f.5
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: pm bus_master cap_list
             configuration: driver=snd_intel8x0 latency=0
             resources: irq:17 ioport:ee00(size=256) ioport:edc0(size=64) memory:feb7fa00-feb7fbff memory:feb7f900-feb7f9ff
     *-scsi:0
          physical id: 1
          logical name: scsi0
          capabilities: emulated
        *-disk
             description: ATA Disk
             product: WDC WD400BB-75FJ
             vendor: Western Digital
             physical id: 0.0.0
             bus info: scsi@0:0.0.0
             logical name: /dev/sda
             version: 3G14
             serial: WD-WCAJA2509362
             size: 37GiB (40GB)
             capabilities: partitioned partitioned:dos
             configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=00050190
           *-volume
                description: Windows FAT volume
                vendor: MSWIN4.1
                physical id: 1
                bus info: scsi@0:0.0.0,1
                logical name: /dev/sda1
                version: FAT32
                serial: 7b31-3af3
                size: 37GiB
                capacity: 37GiB
                capabilities: primary bootable fat initialized
                configuration: FATs=2 filesystem=fat
     *-scsi:1
          physical id: 2
          logical name: scsi1
          capabilities: emulated
        *-cdrom
             description: CD-R/CD-RW writer
             product: CD-R/RW SW-252S
             vendor: SAMSUNG
             physical id: 0.0.0
             bus info: scsi@1:0.0.0
             logical name: /dev/cdrom
             logical name: /dev/cdrw
             logical name: /dev/sr0
             version: R901
             capabilities: removable audio cd-r cd-rw
             configuration: ansiversion=5 status=nodisc
lscpu

Code: Select all

Architecture:        i686
CPU op-mode(s):      32-bit
Byte Order:          Little Endian
CPU(s):              1
On-line CPU(s) list: 0
Thread(s) per core:  1
Core(s) per socket:  1
Socket(s):           1
Vendor ID:           GenuineIntel
CPU family:          15
Model:               2
Model name:          Intel(R) Pentium(R) 4 CPU 2.66GHz
Stepping:            7
CPU MHz:             2659.768
BogoMIPS:            5319.53
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cpuid cid xtpr
inxi

Code: Select all

System:    Host: lubuntu Kernel: 4.15.0-20-generic i686 bits: 32 gcc: 7.3.0 Desktop: LXDE (Openbox 3.6.1)
           Distro: Ubuntu 18.04 LTS
Machine:   Device: desktop System: Dell product: OptiPlex GX270 serial: N/A
           Mobo: Dell model: 0U1324 serial: N/A BIOS: Dell v: A07 date: 06/26/2006
CPU:       Single core Intel Pentium 4 (-UP-) arch: Netburst Willamette rev.7 cache: 512 KB
           flags: (pae sse sse2) bmips: 5319 speed: 2659 MHz (max)
Graphics:  Card: Intel 82865G Integrated Graphics Controller bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Mesa DRI Intel 865G x86/MMX/SSE2 version: 1.3 Mesa 18.0.0-rc5 Direct Render: Yes
Audio:     Card Intel 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller
           driver: snd_intel8x0 ports: ee00 edc0 bus-ID: 00:1f.5
           Sound: Advanced Linux Sound Architecture v: k4.15.0-20-generic
Network:   Card: Intel 82540EM Gigabit Ethernet Controller
           driver: e1000 v: 7.3.21-k8-NAPI port: df40 bus-ID: 01:0c.0
           IF: enp1s12 state: up speed: 1000 Mbps duplex: full mac: 00:0f:1f:7d:4f:3d
Drives:    HDD Total Size: 71.4GB (1.4% used)
           ID-1: /dev/sda model: WDC_WD400BB size: 40.0GB temp: 34C
           ID-2: USB /dev/sdb model: Cruzer_Glide size: 31.4GB temp: 0C
Partition: ID-1: / size: 1002M used: 126M (13%) fs: overlay dev: N/A
           ID-2: swap-1 size: 1.05GB used: 0.00GB (0%) fs: swap dev: /dev/zram0
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 121 Uptime: 15 min Memory: 152.3/2003.3MB Init: systemd runlevel: 5 Gcc sys: N/A
           Client: Shell (bash 4.4.191) inxi: 2.3.56
dmidecode

Code: Select all

# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.3 present.

Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
	Vendor: Dell Computer Corporation
	Version: A07
	Release Date: 06/26/2006
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 512 kB
	Characteristics:
		PCI is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		ESCD support is available
		Boot from CD is supported
		Selectable boot is supported
		EDD is supported
		Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		ACPI is supported
		USB legacy is supported
		AGP is supported
		LS-120 boot is supported
		BIOS boot specification is supported
		Function key-initiated network boot is supported

Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 1
		en|US|iso8859-1
	Currently Installed Language: en|US|iso8859-1
lspci

Code: Select all

00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to I/O Memory Interface (rev 02)
00:1d.0 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
lsscsi

Code: Select all

[0:0:0:0]    disk    ATA      WDC WD400BB-75FJ 3G14  /dev/sda 
[1:0:0:0]    cd/dvd  SAMSUNG  CD-R/RW SW-252S  R901  /dev/sr0 
[4:0:0:0]    disk    SanDisk  Cruzer Glide     1.00  /dev/sdb 
hwinfo <-- this produces too much ouput.

I have to admit I'm a little lost so I'm not sure if this is the right place to submit these results nor do I completely understand the debug log.
I'm not very familiar with the NT architecture so I can't even guess as to where the bug lies.

I would really like to see ReactOS boot on my optiplex gx270 so I can do more testing if needed.

middings
Posts: 1028
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: Real hardware 0.4.9

Post by middings »

qbancoffee, you provided a great deal of information about your Dell Optiplex GX270 computer and almost all of a debug log. The post-crash backtrace appears to be missing from the debug log that you provided.

Take a look at vicmarcal's first post in this topic: [ReadThis]ReactOS doesn't work in my computer!!. The portion of the post that begins "2) A Debug log:" explains how to use the ReactOS debugger's 'bt' command to obtain a post-crash backtrace. Such a backtrace as the last portion of a debug log often provides necessary information that the developers require to solve a crash.

qbancoffee
Posts: 10
Joined: Mon Aug 06, 2018 5:44 pm

Re: Real hardware 0.4.9

Post by qbancoffee »

Hello middings
my apologies, I hadn't seen that post.
Thank you for pointing me in the right direction.

Here is the rest of the info.....
1) Information
- Using install cd
- ReactOS 0.4.9 (Build 20180712-0.4.9-release-0-ga920a96) (Commit a920a9672c5768c66714789a52af0a8255cb5161)
- There is no BSOD. ReactOS 1st stage text based install works and after restarting, the boot menu appears.
After selecting the type of startup, ReactOS(DEBUG), ReactOS(SCREEN), ect... the splash screen comes up and the progress bar
advances all the way to the right. When one expects the graphical install to appear, the monitor flickers and the OS hangs.

2) Debug Log
I selected screen mode and waited for reactos to hang to issue the bt command. Unfortunately nothing extra was generated by issuing that command.
I attempted this several times and even waited about 10 minutes to make sure that the OS wasn't in the middle of something.

I then rebooted and entered the Debug screen and issued the command when it hung. This did produce output on the serial port.

bt command results.

Code: Select all

*** Assertion failed: ppdev->pSurface != NULL
***   Source File: ../../win32ss/gdi/eng/mouse.c, line 52

Break repeatedly, break Once, Ignore, terminate Process or terminate Thread (boipt)? 
kdb:> bt
Execute '.cxr F71CB2F4' to dump context
\0x1b[7h\0x05
Entered debugger on embedded INT3 at 0x0008:0x8094d3ee.
kdb:> 
kdb:> bt
Eip:
<NTOSKRNL.EXE:14d3ef (:0 (DbgBreakPoint))>
Frames:
<win32k.sys:116e6 (win32ss/gdi/eng/mouse.c:52 (MouseSafetyOnDrawStart))>
<win32k.sys:98cc1 (win32ss/gdi/ntgdi/dclife.c:561 (DC_vPrepareDCsForBlit))>
<win32k.sys:b408e (win32ss/gdi/ntgdi/freetype.c:5154 (GreExtTextOutW))>
<win32k.sys:33b4d (win32ss/user/ntuser/desktop.c:1551 (IntPaintDesktop))>
<win32k.sys:35401 (win32ss/user/ntuser/desktop.c:830 (DesktopWindowProc))>
<win32k.sys:53eda (win32ss/user/ntuser/message.c:1378 (co_IntSendMessageTimeoutSingle))>
<win32k.sys:545fb (win32ss/user/ntuser/message.c:1507 (co_IntSendMessageTimeout))>
<win32k.sys:5474e (win32ss/user/ntuser/message.c:1298 (co_IntSendMessage))>
<win32k.sys:66bc6 (win32ss/user/ntuser/painting.c:1520 (IntBeginPaint))>
<win32k.sys:35414 (win32ss/user/ntuser/desktop.c:836 (DesktopWindowProc))>
<win32k.sys:53eda (win32ss/user/ntuser/message.c:1378 (co_IntSendMessageTimeoutSingle))>
<win32k.sys:545fb (win32ss/user/ntuser/message.c:1507 (co_IntSendMessageTimeout))>
<win32k.sys:5474e (win32ss/user/ntuser/message.c:1298 (co_IntSendMessage))>
<win32k.sys:5bc2e (win32ss/user/ntuser/msgqueue.c:954 (co_MsqDispatchOneSentMessage))>
<win32k.sys:5355f (win32ss/user/ntuser/message.c:847 (co_IntPeekMessage))>
<win32k.sys:5397f (win32ss/user/ntuser/message.c:1068 (co_IntGetPeekMessage))>
<win32k.sys:32c63 (win32ss/user/ntuser/desktop.c:919 (DesktopThreadMain))>
<win32k.sys:41f77 (win32ss/user/ntuser/input.c:347 (CreateSystemThreads))>
<win32k.sys:6e531 (win32ss/user/ntuser/simplecall.c:394 (NtUserCallOneParam))>
<NTOSKRNL.EXE:131a3e (ntoskrnl/include/internal/i386/ke.h:712 (KiSystemServiceHandler))>--- Press q to abort, any other key to continue ---

<NTOSKRNL.EXE:3da9 (:0 (KiFastCallEntry))>
<ntdll.dll:de45>
<00000000>
kdb:> 
Going through these steps and reading(but not understanding) the debug info helped because my subconscious produced a gut feeling
that the problem may lie in the VGA configuration. I entered the BIOS and changed the "Onboard Video Buffer" setting from 1 MB to 8 MB
and attempted to boot. Unfortunately ReactOS did not start but the debug info was different. Thinking that the installation was hosed, I reinstalled the OS and it booted to the graphical install and after installing, it booted to the desktop.
This was very satisfying......
Since discovering this, I've reinstalled the OS multiple times with the 1 MB setting and
I can confirm that on this computer, the ReactOS installer will not continue with a 1 MB video buffer .
Everything works when the video buffer is set to 8MB

I'm not sure if the video buffer size is specified somewhere else but it isn't in the "Installing ReacOS" wiki.
https://reactos.org/wiki/Installing_ReactOS

Do you know if there is a minimum video memory requirement?

I'm excited to keep testing and hopefully I can add this the PC ROS rigs wiki.

Thanks for you help.

qbancoffee
Posts: 10
Joined: Mon Aug 06, 2018 5:44 pm

Re: Real hardware 0.4.9

Post by qbancoffee »

I want to add that with the video buffer set to 1 MB in the BIOS I can run Ubuntu 18.04 32bit version and I can install and run Windows XP Professional with SP2.
I don't know if there is a minimum requirement for the video buffer but this behaviour might qualify as a bug if it's supposed to behave like Windows server 2003 or Windows XP.
I searched JIRA but I couldn't find anything like this. I'll do some more research to decide if this is a bug and then file it if so.

middings
Posts: 1028
Joined: Tue May 07, 2013 9:18 pm
Location: California, USA

Re: Real hardware 0.4.9

Post by middings »

qbancoffee wrote:
Sun Aug 19, 2018 7:56 pm
Do you know if there is a minimum video memory requirement?
I do not know if ReactOS has a minimum video memory requirement larger than that of Microsoft Windows XP/Server 2003. If ReactOS does, it is either a bug in ReactOS or setup problem with your PC. I used the ReactOS Forum search tool (in the upper right corner of this web page) to see if a "minimum video memory" requirement has been mentioned in the past few years. None of the results returned looked helpful to me. Then, I used Bing to search the entire ReactOS web site (site:ReactOS.org minimum video memory). I do not know if those results will help.

This weekend the top ReactOS developers have gathered at ReactOS Hackfest 2018 in Berlin. Maybe one of them will take a look at your posts soon. You have encountered an interesting problem.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 2 guests