Request for testing on real hardware
Moderator: Moderator Team
Re: Request for testing on real hardware
I am planning to test random but often crashes while browsing with FireFox 3.0 on my realHW. But first want to make sound work(actually i will not fix it, i will test it to help in fixing). So it will be possible to use reactOS for listening music, browsing internet, etc. I hope i will start testing Firefox crashes (still have no idea what is guilty: kernel, win32ss or network) in a few days.
-
- Posts: 420
- Joined: Tue Sep 16, 2008 1:13 pm
Re: Request for testing on real hardware
Can you make a log via serial port and nullmodem-cable ?
If you don't have a serial port, you should organize are serial PCI Card (cost only a couple of euros), that should work now, because you can pass Com-Port Adresses.
Look in forum there is an actual new post to this item.
It's also possible to write the log to the harddisk via Kernelparameters. See same post
If you don't have a serial port, you should organize are serial PCI Card (cost only a couple of euros), that should work now, because you can pass Com-Port Adresses.
Look in forum there is an actual new post to this item.
It's also possible to write the log to the harddisk via Kernelparameters. See same post
Re: Request for testing on real hardware
Getting debug info is not problem for me
Re: Request for testing on real hardware
Here is a new bug report on an Ethernet controller bug:
http://www.reactos.org/bugzilla/show_bug.cgi?id=6686
http://www.reactos.org/bugzilla/show_bug.cgi?id=6686
Re: Request for testing on real hardware
Tried LiveCD revision 54496 - just one blank black screen.
Re: Request for testing on real hardware
System specs:
CPU: Intel Pentium D @ 3.40 GHz, RAM: 1024MB, HDD: 40GB PATA
Motherboard: MSI 865GM3-V, Chipset: Intel 865G/ICH5, NIC: Realtek 8100C
Keyboard: HP KB-0316 PS2, Mouse: Microsoft USB
First install:
Selected ACPI PC Multiprocessor. Got "Error loading imported dll" during Loading KDCOM.DLL regardless of selected boot options.
Second install:
Selected ACPI PC Uniprocessor this time. USB mouse did not work at all. PS2 keyboard barley worked, no status LED's, was unable to alt + tab between applications. Basically all I could do was play with the startmenu and shutdown the machine.
CPU: Intel Pentium D @ 3.40 GHz, RAM: 1024MB, HDD: 40GB PATA
Motherboard: MSI 865GM3-V, Chipset: Intel 865G/ICH5, NIC: Realtek 8100C
Keyboard: HP KB-0316 PS2, Mouse: Microsoft USB
First install:
Selected ACPI PC Multiprocessor. Got "Error loading imported dll" during Loading KDCOM.DLL regardless of selected boot options.
Second install:
Selected ACPI PC Uniprocessor this time. USB mouse did not work at all. PS2 keyboard barley worked, no status LED's, was unable to alt + tab between applications. Basically all I could do was play with the startmenu and shutdown the machine.
Re: Request for testing on real hardware
System specs:
CPU: Intel Pentium 2 @ 300 MHz, RAM: 192 MB, HDD: 10GB PATA
Motherboard: Gigabyte GA-686LX3, Chipset: Intel 440LX, NIC: None
Keyboard: IBM KS-8825 USB, Mouse: Lenovo USB
USB mouse did not work at all. Keyboard status lights did not work properly. System froze after a minute or so.
CPU: Intel Pentium 2 @ 300 MHz, RAM: 192 MB, HDD: 10GB PATA
Motherboard: Gigabyte GA-686LX3, Chipset: Intel 440LX, NIC: None
Keyboard: IBM KS-8825 USB, Mouse: Lenovo USB
USB mouse did not work at all. Keyboard status lights did not work properly. System froze after a minute or so.
Re: Request for testing on real hardware
AMD Athlon(tm) 64 X2 Dual Core Processor 4000+
NVIDIA GeForce 8100 / nForce 720a
BIOSTAR Group GF8100 M2+ TE
It does not work.
NVIDIA GeForce 8100 / nForce 720a
BIOSTAR Group GF8100 M2+ TE
It does not work.
Re: Request for testing on real hardware
Exactly my configuration. And the same result.Karl Mark wrote:NVIDIA GeForce 8100 / nForce 720a
BIOSTAR Group GF8100 M2+ TE
It does not work.
Re: Request for testing on real hardware
Try enabling IDE compatibility mode in your bios. That is the most common problem since every machine has a completely different SATA controller chipset these days.
Re: Request for testing on real hardware
One of the previous builds showed at least blue screen with problem description. Now - only blank screen. Black. I don't think it's connected with compatibility mode.SomeGuy wrote:Try enabling IDE compatibility mode in your bios. That is the most common problem since every machine has a completely different SATA controller chipset these days.
Who is online
Users browsing this forum: Bing [Bot] and 50 guests