ReactOS does not run on older computers
Moderator: Moderator Team
From an actual topic: [http://www.reactos.org/forum/viewtopic.php?t=3297]]PeterK wrote:My last (and also first..) bug report experience was burried in bugzilla half a year ago - I'm happy to talk to people here !
GreatLord wrote:at moment it is around 4xx bugs open. and I often have time deal with 2-3 patch for review. and commit allot translations patch. and close around 10-20 bugs report each time I review bugzila. be pentinets, we are not many devloper in reactos that is active same time. around 5-10 devloper.
Last edited by florian on Sun Jan 07, 2007 1:49 pm, edited 3 times in total.
Remote debugging session, part 3BootCD switches to an invalid video mode
Try to use ReactOS2.iso.7z from http://www.5748.nm.ru/iso/ There should be edit box and you can enter any letter from a to t (any other character means no checks). You will see on which stage this bug occurs.
On K7S41GX (AMD +1500):hto wrote:Try to use ReactOS2.iso.7z ..
A - black screen, no "invalid sync", cdrom, HD and floppy LED are on, no activity ! (why?)
B - invalid sync (cdrom, HD and floppy LED are on !)
(I didn't go on as I think I have the expected effect !?)
Report about other PCs later ..
***** appended later : *****
On mainboard Biostar M5ATA (ALI 154x chipset, MMX200):
I can just type anything to boot from cdrom, but when Your input window (ok, ok, it's DOS..) appears, computer does not react on any key pressed. Inside cdrom You hear a silent noise like laser tries to get track again and again ..
As it should be. "A" means halt in blue.sys before any access to videoregisters.A - black screen, no "invalid sync", cdrom, HD and floppy LED are on, no activity ! (why?)
Yes. I see blue.sys writes strange value e3 to videoregister 3c2 ("miscellaneous output"). My book says it should be 23. It was introduced in rev. 24464. There was no changes between 24000 and 24400.B - invalid sync (cdrom, HD and floppy LED are on !)
(I didn't go on as I think I have the expected effect !?)
No, it's ReactOS bootloader, not DOS. I don't know why this happens.On mainboard Biostar M5ATA (ALI 154x chipset, MMX200):
I can just type anything to boot from cdrom, but when Your input window (ok, ok, it's DOS..) appears, computer does not react on any key pressed.
Maybe bad sector on CD or faulty drive...Inside cdrom You hear a silent noise like laser tries to get track again and again ..
Yep, sounds like the monitor complaining about driving at the wrong sync frequency.dark wrote:
"invalid sync" and related error messages seem to be from the computers' monitors. (mine says "out of range") Seems as though the kernel is using non standard text display screen options.
Yes, this is the message that the MONITOR shows on screen - not ReactOS !
A good reason to have a nice boot menu offering standard 640x480 VGA safe mode perhaps? (or maybe 800x600 as time has moved on since the mid 90s!)
Value of 23 does not work. Right value is 67. There is DOS program testmisc.exe, you can try to run it as testmisc 67 and see.My book says it should be 23.
http://www.5748.nm.ru/testbios/
I have out of sync with incorrect value e3, which ReactOS driver now uses.
bootCD-dbg 24350 is ok on mainboard K7S41GX (up to SETUP text)hto wrote:There was no changes between 24000 and 24400.
bootCD-dbg 24370 is not => "invalid sync" ..
Change must have happened between 24350 and 24370.
No, I don't think so. Drive's ok, CD is always the same (RW) and does work on the other PC as described. (I do use 3 RW, one by one they are used to burn the ISO files onto them)hto wrote:Maybe bad sector on CD or faulty drive...
What happens on MMX 200 biostar mainbord,
is perhaps a different bug.PeterK wrote:.. computer does not react on any key pressed. ..
So let's first see what happens if correct video mode is set ..
There is new blue.sys driver: http://www.5748.nm.ru/iso/
You can replace reactos\blue.sys on BootCD with it and try to boot.
There is another blue.sys: http://www.5748.nm.ru/iso/test/
Use for testing with ReactOS2.iso.7z.
You can replace reactos\blue.sys on BootCD with it and try to boot.
There is another blue.sys: http://www.5748.nm.ru/iso/test/
Use for testing with ReactOS2.iso.7z.
Okay.hto wrote:There is another blue.sys: http://www.5748.nm.ru/iso/test/
Use for testing with ReactOS2.iso.7z.
Whatfor is that ?hto wrote:There is new blue.sys driver: http://www.5748.nm.ru/iso/
You can replace reactos\blue.sys on BootCD with it and try to boot.
Can I try it with the actual SVN bootCD 25399 ?
This is an interesting technical resource for std VGA modes and sync info - might be of interest.
http://www.epanorama.net/documents/pc/vga_timing.html
I see that 700x400 letterbox is VGA-400 whilst the popular 640x480 mode is VGA-480 etc...
http://www.epanorama.net/documents/pc/vga_timing.html
I see that 700x400 letterbox is VGA-400 whilst the popular 640x480 mode is VGA-480 etc...
There are the 3 "standard" VGA modes that each VGA card is supposed to be able to do:
* 640 x 350 x 70 is compatible with the old EGA mode, but on a VGA display.
* 640 x 400 x 70 is the MS-DOS text mode (when the computer is booting !).
* 640 x 480 x 60 is the default Windows(tm) graphics mode (16 colours !).
Their line frequency is exactly twice that of the NTSC television system, or almost twice that of the PAL television system. This makes it fairly easy to implement a VGA input on a television set that uses line doubling for the television signals so the line deflection already runs on 31 kHz.
The following timings come from a list of 82 different computer timings, and by now there will be even more. Some video cards even have variable timing (allowing the user to set width, height and shift...). The only standard is that there is no standard !
Who is online
Users browsing this forum: No registered users and 11 guests