ReactOS 0.3.10 on Industrial CPU board
Moderator: Moderator Team
ReactOS 0.3.10 on Industrial CPU board
Hi all
Downloaded iso image and booted cdrom on a:
ISA VIA MARK Half Size Single Board Computer
CPU:VIA MARK 533 MHz 686B
Bios: Award
On board VGA and all other ports (IDE, CFC, USB,Serial etc)
The cd booted OK, and read all the files in a 640x480 screen, and then
switched screen mode, and locked up.
This cpu will boot Windows, although I havent done it.It is generally used
by the industrial world for that purpose.
I currently run FreeDos with cwsdpmi and gui app's compiled with FreeBasic without any problems.
It will also run all flavors of DOS, and never had compatibility issues.
Any suggestions, or am I pushing my luck asking for compatibility on this cpu.
Other than the cd image, is there any minimal boot image that will hilight the issues.
Regards
Downloaded iso image and booted cdrom on a:
ISA VIA MARK Half Size Single Board Computer
CPU:VIA MARK 533 MHz 686B
Bios: Award
On board VGA and all other ports (IDE, CFC, USB,Serial etc)
The cd booted OK, and read all the files in a 640x480 screen, and then
switched screen mode, and locked up.
This cpu will boot Windows, although I havent done it.It is generally used
by the industrial world for that purpose.
I currently run FreeDos with cwsdpmi and gui app's compiled with FreeBasic without any problems.
It will also run all flavors of DOS, and never had compatibility issues.
Any suggestions, or am I pushing my luck asking for compatibility on this cpu.
Other than the cd image, is there any minimal boot image that will hilight the issues.
Regards
-
- Test Team
- Posts: 802
- Joined: Thu Apr 03, 2008 2:17 pm
- Contact:
Re: ReactOS 0.3.10 on Industrial CPU board
Hi Dinosaur, it's likely that there may be issues with the VGA adapter. Since it's embedded, could you describe the chipset? Also, are you booting into an IPC that happens to have a SATA disk? These may be the two points of failure for your particular set up. If possible, could you provide a debug log? See http://www.reactos.org/wiki/index.php/D ... erial_Port
Embedded applications like POS systems are one of the areas which we are trying to target, so your help in trying to get this to work on the VIA board will benefit us. If possible, would your firm be interested in committing some resources to help us achieve our objectives?
Embedded applications like POS systems are one of the areas which we are trying to target, so your help in trying to get this to work on the VIA board will benefit us. If possible, would your firm be interested in committing some resources to help us achieve our objectives?
Last edited by Lone_Rifle on Sun Jul 12, 2009 10:06 pm, edited 1 time in total.
Re: ReactOS 0.3.10 on Industrial CPU board
A possibly useful link:
http://www.reactos.org/wiki/index.php/S ... ideo_cards
As a side note, I put it to the mods that we could really do with a sticky thread containing links to the various "Supported Hardware" wiki pages so as to make things easier for new users who are wondering about compatibility.
http://www.reactos.org/wiki/index.php/S ... ideo_cards
As a side note, I put it to the mods that we could really do with a sticky thread containing links to the various "Supported Hardware" wiki pages so as to make things easier for new users who are wondering about compatibility.
Re: ReactOS 0.3.10 on Industrial CPU board
Hi all
Thanks for the responses.
Sorry for the shortage of detail.
The iso image was a bootcd, (the other needs Windows to run) and the chipset for the vga is also listed as VIA MARK.
After looking at the serial cable link, yes I can get a debug log.
Will post when I have done it.
My applications are mainly in Industrial Weighing not POS, but regardless,
I am happy to help (within my capabilities).
The cpu board has an onboard ide & compact Flash adapter. I normally boot from the CFC.
However on this occasion I used a 40 way ribbon on the ide adapter for the CD.
Below some more info, which may mean something, particularly the vendor detail.Regards
Thanks for the responses.
Sorry for the shortage of detail.
The iso image was a bootcd, (the other needs Windows to run) and the chipset for the vga is also listed as VIA MARK.
After looking at the serial cable link, yes I can get a debug log.
Will post when I have done it.
My applications are mainly in Industrial Weighing not POS, but regardless,
I am happy to help (within my capabilities).
The cpu board has an onboard ide & compact Flash adapter. I normally boot from the CFC.
However on this occasion I used a 40 way ribbon on the ide adapter for the CD.
Below some more info, which may mean something, particularly the vendor detail.
Code: Select all
PCI Bus Nbr Device Nbr Func Nbr Vendor Device Class Device Class IRQ
1 0 0 5333 8D01 0300 Display Ctrlr N/A
0 7 1 1106 0571 0101 IDE Ctrlr 14
Re: ReactOS 0.3.10 on Industrial CPU board
Hi all
The serial port dump below.It is worth noting that at this point the display is blank, and the only reason I know it is in debug mode is by other PC
with Hyper Terminal. At one stage I got further, to the point of nominating language etc and then at filecopy stage
it went blank. Note that most Industrial cpu boards have lcd connectors(lvds) as well as vga. The bios allows the setting of resolution
which then applies to LCD or CRT. I have changed the Bios settings to force the display to CRT mode, but cant get any further.
Perhaps the detail above will hilight the problem.
REgards
The serial port dump below.
Code: Select all
(ntoskrnl\kd\kdio.c:220) -----------------------------------------------------
(ntoskrnl\kd\kdio.c:221) ReactOS 0.3.10 (Build 20090702-r41747)
(ntoskrnl\kd\kdio.c:222) Command Line: NOGUIBOOT DEBUGPORT=COM1 NOGUIBOOT DEBU
GPORT=COM1
(ntoskrnl\kd\kdio.c:223) ARC Paths: multi(0)disk(0)cdrom(159) \ multi(0)disk(0)c
drom(159) \reactos\
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
Used memory 114292Kb
(ntoskrnl\mm\mminit.c:284) Start End Type
(ntoskrnl\mm\mminit.c:285) 0x80000000 - 0x80800000 Undefined region
(ntoskrnl\mm\mminit.c:288) 0x80800000 - 0x80E00000 FreeLDR Kernel mapping r
egion
(ntoskrnl\mm\mminit.c:291) 0x80E00000 - 0x80EE0000 PFN Database region
(ntoskrnl\mm\mminit.c:298) 0x80EE0000 - 0x872E0000 Non paged pool region
(ntoskrnl\mm\mminit.c:301) 0x872E0000 - 0x8D6E0000 Paged pool region
WARNING: KdDebuggerInitialize1 at drivers\base\kdcom\i386\kdbg.c:489 is UNIMPLE
MENTED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\BUSLOGIC' initialization failed, stat
us (0xc00000c0)
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\FLOPPY' initialization failed, status
(0xc000000e)
(drivers\storage\class\ramdisk\ramdisk.c:2310) RAM Disk Driver Initialized
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(base\setup\usetup\interface\devinst.c:371) Device arrival event: Root\*PNP0F13\
0000
(base\setup\usetup\interface\devinst.c:371) Device arrival event: Root\*PNP0501\
0001
(base\setup\usetup\interface\devinst.c:371) Device arrival event: Root\*PNP0501\
0000
(base\setup\usetup\interface\devinst.c:371) Device arrival event: Root\*PNP0A03\
0001
(base\setup\usetup\interface\devinst.c:84) Using driver 'pci.sys' for device 'Ro
ot\*PNP0A03\0001'
(base\setup\usetup\interface\devinst.c:371) Device arrival event: Root\*PNP0A03\
0000
(base\setup\usetup\interface\devinst.c:84) Using driver 'pci.sys' for device 'Ro
ot\*PNP0A03\0000'
(base\setup\usetup\interface\devinst.c:371) Device arrival event: Root\*PNP0303\
0000
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_10EC&D
EV_8139&SUBSYS_813910EC&REV_10\1&e8188ae5&0D
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_1106&D
EV_3057&SUBSYS_30571106&REV_40\1&e8188ae5&87
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_1106&D
EV_3038&SUBSYS_12340925&REV_1A\1&e8188ae5&67
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_1106&D
EV_3038&SUBSYS_12340925&REV_1A\1&e8188ae5&47
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_1106&D
EV_0571&SUBSYS_05711106&REV_06\1&e8188ae5&27
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_1106&D
EV_0686&SUBSYS_00001106&REV_40\1&e8188ae5&07
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_1106&D
EV_8605&SUBSYS_00000000&REV_00\1&e8188ae5&01
(base\setup\usetup\interface\devinst.c:84) Using driver 'pci.sys' for device 'PC
I\VEN_1106&DEV_8605&SUBSYS_00000000&REV_00\1&e8188ae5&01'
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_1106&D
EV_0605&SUBSYS_06051106&REV_00\1&e8188ae5&00
(base\setup\usetup\interface\devinst.c:371) Device arrival event: PCI\VEN_5333&D
EV_8D01&SUBSYS_70000000&REV_02\2&67712f3&00
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(drivers\filesystems\cdfs\common.c:107) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:574) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:454) CdfsVerifyVolume() called
(ntoskrnl\ex\resource.c:144) EX: resource: APCs still enabled before resource 81
0EBB30 acquire !!!
Entered debugger on embedded INT3 at 0x0008:0x808bf5c6.
kdb:>
(ntoskrnl\kd\kdio.c:220) -----------------------------------------------------
(ntoskrnl\kd\kdio.c:221) ReactOS 0.3.10 (Build 20090702-r41747)
(ntoskrnl\kd\kdio.c:222) Command Line: NOGUIBOOT DEBUGPORT=COM1 NOGUIBOOT DEBU
GPORT=COM1
(ntoskrnl\kd\kdio.c:223) ARC Paths: multi(0)disk(0)cdrom(159) \ multi(0)disk(0)c
drom(159) \reactos\
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
Used memory 114292Kb
(ntoskrnl\mm\mminit.c:284) Start End Type
(ntoskrnl\mm\mminit.c:285) 0x80000000 - 0x80800000 Undefined region
(ntoskrnl\mm\mminit.c:288) 0x80800000 - 0x80E00000 FreeLDR Kernel mapping r
egion
(ntoskrnl\mm\mminit.c:291) 0x80E00000 - 0x80EE0000 PFN Database region
(ntoskrnl\mm\mminit.c:298) 0x80EE0000 - 0x872E0000 Non paged pool region
(ntoskrnl\mm\mminit.c:301) 0x872E0000 - 0x8D6E0000 Paged pool region
WARNING: KdDebuggerInitialize1 at drivers\base\kdcom\i386\kdbg.c:489 is UNIMPLE
MENTED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\BUSLOGIC' initialization failed, stat
us (0xc00000c0)
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\FLOPPY' initialization failed, status
(0xc000000e)
(drivers\storage\class\ramdisk\ramdisk.c:2310) RAM Disk Driver Initialized
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(drivers\filesystems\cdfs\common.c:107) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:574) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:454) CdfsVerifyVolume() called
(drivers\filesystems\cdfs\fsctl.c:474) Volume has been verified!
(drivers\filesystems\cdfs\common.c:112) IoVerifyVolume() returned (Status 0)
(ntoskrnl\cc\copy.c:221) IoPageRead failed, Status 80000016
*** Fatal System Error: 0x0000006b
(0xC0000001,0x00000002,0x00000000,0x00000000)
Entered debugger on embedded INT3 at 0x0008:0x808bf5cc.
kdb:>
(ntoskrnl\kd\kdio.c:220) -----------------------------------------------------
(ntoskrnl\kd\kdio.c:221) ReactOS 0.3.10 (Build 20090702-r41747)
(ntoskrnl\kd\kdio.c:222) Command Line: NOGUIBOOT DEBUGPORT=COM1 NOGUIBOOT DEBU
GPORT=COM1
(ntoskrnl\kd\kdio.c:223) ARC Paths: multi(0)disk(0)cdrom(159) \ multi(0)disk(0)c
drom(159) \reactos\
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
Used memory 114292Kb
(ntoskrnl\mm\mminit.c:284) Start End Type
(ntoskrnl\mm\mminit.c:285) 0x80000000 - 0x80800000 Undefined region
(ntoskrnl\mm\mminit.c:288) 0x80800000 - 0x80E00000 FreeLDR Kernel mapping r
egion
(ntoskrnl\mm\mminit.c:291) 0x80E00000 - 0x80EE0000 PFN Database region
(ntoskrnl\mm\mminit.c:298) 0x80EE0000 - 0x872E0000 Non paged pool region
(ntoskrnl\mm\mminit.c:301) 0x872E0000 - 0x8D6E0000 Paged pool region
WARNING: KdDebuggerInitialize1 at drivers\base\kdcom\i386\kdbg.c:489 is UNIMPLE
MENTED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\BUSLOGIC' initialization failed, stat
us (0xc00000c0)
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\FLOPPY' initialization failed, status
(0xc000000e)
(drivers\storage\class\ramdisk\ramdisk.c:2310) RAM Disk Driver Initialized
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(drivers\filesystems\cdfs\common.c:107) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:574) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:454) CdfsVerifyVolume() called
(drivers\filesystems\cdfs\fsctl.c:474) Volume has been verified!
(drivers\filesystems\cdfs\common.c:112) IoVerifyVolume() returned (Status 0)
(ntoskrnl\cc\copy.c:388) ReadCacheSegmentChain failed, Status 80000016
(lib\rtl\process.c:58) Failed to create section for image file
(lib\rtl\process.c:207) Could not map process image
*** Fatal System Error: 0x0000006f
(0x80000016,0x00000000,0x00000000,0x00000000)
Entered debugger on embedded INT3 at 0x0008:0x808bf5cc.
kdb:>
(ntoskrnl\kd\kdio.c:220) -----------------------------------------------------
(ntoskrnl\kd\kdio.c:221) ReactOS 0.3.10 (Build 20090702-r41747)
(ntoskrnl\kd\kdio.c:222) Command Line: NOGUIBOOT DEBUGPORT=COM1 NOGUIBOOT DEBU
GPORT=COM1
(ntoskrnl\kd\kdio.c:223) ARC Paths: multi(0)disk(0)cdrom(159) \ multi(0)disk(0)c
drom(159) \reactos\
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
Used memory 114228Kb
(ntoskrnl\mm\mminit.c:284) Start End Type
(ntoskrnl\mm\mminit.c:285) 0x80000000 - 0x80800000 Undefined region
(ntoskrnl\mm\mminit.c:288) 0x80800000 - 0x80E00000 FreeLDR Kernel mapping r
egion
(ntoskrnl\mm\mminit.c:291) 0x80E00000 - 0x80EE0000 PFN Database region
(ntoskrnl\mm\mminit.c:298) 0x80EE0000 - 0x872E0000 Non paged pool region
(ntoskrnl\mm\mminit.c:301) 0x872E0000 - 0x8D6E0000 Paged pool region
WARNING: KdDebuggerInitialize1 at drivers\base\kdcom\i386\kdbg.c:489 is UNIMPLE
MENTED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\BUSLOGIC' initialization failed, stat
us (0xc00000c0)
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\FLOPPY' initialization failed, status
(0xc000000e)
(drivers\storage\class\ramdisk\ramdisk.c:2310) RAM Disk Driver Initialized
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(drivers\filesystems\cdfs\common.c:107) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:574) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:454) CdfsVerifyVolume() called
(drivers\filesystems\cdfs\fsctl.c:474) Volume has been verified!
(drivers\filesystems\cdfs\common.c:112) IoVerifyVolume() returned (Status 0)
(ntoskrnl\cc\copy.c:221) IoPageRead failed, Status 80000016
*** Fatal System Error: 0x0000006b
(0xC0000001,0x00000002,0x00000000,0x00000000)
Entered debugger on embedded INT3 at 0x0008:0x808bf5cc.
kdb:>
(ntoskrnl\kd\kdio.c:220) -----------------------------------------------------
(ntoskrnl\kd\kdio.c:221) ReactOS 0.3.10 (Build 20090702-r41747)
(ntoskrnl\kd\kdio.c:222) Command Line: NOGUIBOOT DEBUGPORT=COM1 NOGUIBOOT DEBU
GPORT=COM1
(ntoskrnl\kd\kdio.c:223) ARC Paths: multi(0)disk(0)cdrom(159) \ multi(0)disk(0)c
drom(159) \reactos\
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
Used memory 114228Kb
(ntoskrnl\mm\mminit.c:284) Start End Type
(ntoskrnl\mm\mminit.c:285) 0x80000000 - 0x80800000 Undefined region
(ntoskrnl\mm\mminit.c:288) 0x80800000 - 0x80E00000 FreeLDR Kernel mapping r
egion
(ntoskrnl\mm\mminit.c:291) 0x80E00000 - 0x80EE0000 PFN Database region
(ntoskrnl\mm\mminit.c:298) 0x80EE0000 - 0x872E0000 Non paged pool region
(ntoskrnl\mm\mminit.c:301) 0x872E0000 - 0x8D6E0000 Paged pool region
WARNING: KdDebuggerInitialize1 at drivers\base\kdcom\i386\kdbg.c:489 is UNIMPLE
MENTED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\BUSLOGIC' initialization failed, stat
us (0xc00000c0)
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\FLOPPY' initialization failed, status
(0xc000000e)
(drivers\storage\class\ramdisk\ramdisk.c:2310) RAM Disk Driver Initialized
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(drivers\filesystems\cdfs\common.c:107) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:574) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:454) CdfsVerifyVolume() called
(drivers\filesystems\cdfs\fsctl.c:474) Volume has been verified!
(drivers\filesystems\cdfs\common.c:112) IoVerifyVolume() returned (Status 0)
(ntoskrnl\cc\copy.c:221) IoPageRead failed, Status 80000016
*** Fatal System Error: 0x0000006b
(0xC0000001,0x00000002,0x00000000,0x00000000)
Entered debugger on embedded INT3 at 0x0008:0x808bf5cc.
kdb:>
(ntoskrnl\kd\kdio.c:220) -----------------------------------------------------
(ntoskrnl\kd\kdio.c:221) ReactOS 0.3.10 (Build 20090702-r41747)
(ntoskrnl\kd\kdio.c:222) Command Line: NOGUIBOOT DEBUGPORT=COM1 NOGUIBOOT DEBU
GPORT=COM1
(ntoskrnl\kd\kdio.c:223) ARC Paths: multi(0)disk(0)cdrom(159) \ multi(0)disk(0)c
drom(159) \reactos\
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
(ntoskrnl\ke\i386\cpu.c:229) Centaur CPU support not fully tested!
Used memory 114228Kb
(ntoskrnl\mm\mminit.c:284) Start End Type
(ntoskrnl\mm\mminit.c:285) 0x80000000 - 0x80800000 Undefined region
(ntoskrnl\mm\mminit.c:288) 0x80800000 - 0x80E00000 FreeLDR Kernel mapping r
egion
(ntoskrnl\mm\mminit.c:291) 0x80E00000 - 0x80EE0000 PFN Database region
(ntoskrnl\mm\mminit.c:298) 0x80EE0000 - 0x872E0000 Non paged pool region
(ntoskrnl\mm\mminit.c:301) 0x872E0000 - 0x8D6E0000 Paged pool region
WARNING: KdDebuggerInitialize1 at drivers\base\kdcom\i386\kdbg.c:489 is UNIMPLE
MENTED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
WARNING: IoReportResourceUsage at ntoskrnl\io\iomgr\iorsrce.c:700 is UNIMPLEMEN
TED!
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\BUSLOGIC' initialization failed, stat
us (0xc00000c0)
(ntoskrnl\io\iomgr\driver.c:1392) '\Driver\FLOPPY' initialization failed, status
(0xc000000e)
(drivers\storage\class\ramdisk\ramdisk.c:2310) RAM Disk Driver Initialized
(drivers\filesystems\cdfs\common.c:107) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:574) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:454) CdfsVerifyVolume() called
(drivers\filesystems\cdfs\fsctl.c:474) Volume has been verified!
(drivers\filesystems\cdfs\common.c:112) IoVerifyVolume() returned (Status 0)
(ntoskrnl\cc\copy.c:221) IoPageRead failed, Status 80000016
(drivers\filesystems\cdfs\common.c:196) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:574) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:454) CdfsVerifyVolume() called
(drivers\filesystems\cdfs\fsctl.c:474) Volume has been verified!
(drivers\filesystems\cdfs\common.c:201) IoVerifyVolume() returned (Status 0)
(drivers\filesystems\cdfs\create.c:148) Status 80000016
(ntoskrnl\io\iomgr\file.c:414) Using IopParseDevice() hack
(drivers\filesystems\cdfs\common.c:196) STATUS_VERIFY_REQUIRED
(drivers\filesystems\cdfs\fsctl.c:574) CDFS: IRP_MN_VERIFY_VOLUME
(drivers\filesystems\cdfs\fsctl.c:454) CdfsVerifyVolume() called
(drivers\filesystems\cdfs\fsctl.c:479) Device object 810EBA78 Device to verify
810EBA78
(drivers\filesystems\cdfs\fsctl.c:496) Different volume!
(drivers\filesystems\cdfs\fsctl.c:503) OpenFile \ RefCount 1
(drivers\filesystems\cdfs\common.c:201) IoVerifyVolume() returned (Status c00000
12)
(drivers\filesystems\cdfs\create.c:148) Status 80000016
*** Fatal System Error: 0x0000006b
(0x80000016,0x00000002,0x00000000,0x00000000)
Entered debugger on embedded INT3 at 0x0008:0x808bf5cc.
kdb:>
with Hyper Terminal. At one stage I got further, to the point of nominating language etc and then at filecopy stage
it went blank. Note that most Industrial cpu boards have lcd connectors(lvds) as well as vga. The bios allows the setting of resolution
which then applies to LCD or CRT. I have changed the Bios settings to force the display to CRT mode, but cant get any further.
Perhaps the detail above will hilight the problem.
REgards
No, it is bootable just like BootCD.Dinosaur wrote: (the other needs Windows to run)
I've just looked into uniata.sys sources; when UniataChipDetect() detects VIA82C571, it does goto for_ugly_chips; maybe it means that this chip is not well-supported. Try to remove / delete uniata.sys file and rename / copy atapi.sys (old driver) to uniata.sys.The cpu board has an onboard ide
Please enter bt command to get backtrace.Entered debugger on embedded INT3 at 0x0008:0x808bf5cc.
kdb:>
ReactOS' vbemp.sys driver requires VBE 2.0 support in video-BIOS. Also, the frame buffer size in BIOS Setup should be set to at least 1 MB. If there will be any problems (in the future, on this early stage it is not yet important) with vbemp.sys driver, rename / remove vbemp.sys file so vgamp.sys will be used instead.The bios allows the setting of resolution which then applies to LCD or CRT. I have changed the Bios settings to force the display to CRT mode, but cant get any further.
Re: ReactOS 0.3.10 on Industrial CPU board
Hi
Firstly the bt resultTo make the changes you suggested means not booting from a Cd. This means installing on HDD.
Then connecting that HDD to the second system.
Is there a facility within ReactOS to make a second system from the first ?
REgards
Firstly the bt result
Code: Select all
Entered debugger on embedded INT3 at 0x0008:0x808bf5cc.
kdb:> bt
Eip:
<NTOSKRNL.EXE:bf5cd (lib\rtl\i386\debug_asm.S:42 (RtlpBreakWithStatusInstruction
))>
Frames:
<NTOSKRNL.EXE:673d (ntoskrnl/ke/bug.c:1089 (KeBugCheckWithTf@24))>
<NTOSKRNL.EXE:69d3 (ntoskrnl/ke/bug.c:1398 (KeBugCheck@4))>
<NTOSKRNL.EXE:a7903 (ntoskrnl/ps/psmgr.c:322 (PsLocateSystemDll@0))>
<NTOSKRNL.EXE:d809c (ntoskrnl/io/iomgr/iomgr.c:563 (IoInitSystem@4))>
<NTOSKRNL.EXE:363c9 (ntoskrnl/ex/init.c:1711 (Phase1InitializationDiscard@4))>
<NTOSKRNL.EXE:370ea (ntoskrnl/ex/init.c:1921 (Phase1Initialization@4))>
<NTOSKRNL.EXE:ad3d9 (ntoskrnl/ps/thread.c:159 (PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:b73c2 (ntoskrnl\ke\i386\ctxswitch.S:306 (KiThreadStartup@156))>
kdb:>
Then connecting that HDD to the second system.
Is there a facility within ReactOS to make a second system from the first ?
REgards
-
- Test Team
- Posts: 802
- Joined: Thu Apr 03, 2008 2:17 pm
- Contact:
Re: ReactOS 0.3.10 on Industrial CPU board
Or you could extract all the files from the CD, make the change and burn a new CD, although you'll also have to work out how to extract the boot sector for use in the 2nd CD..Dinosaur wrote:To make the changes you suggested means not booting from a Cd.
There are some programs which allow to edit CD images.Lone_Rifle wrote: Or you could extract all the files from the CD, make the change and burn a new CD, although you'll also have to work out how to extract the boot sector for use in the 2nd CD..
I do not understand.Dinosaur wrote: Is there a facility within ReactOS to make a second system from the first ?
You can install ReactOS on another (either real or virtual) machine, then manually copy files to HD. One complication is how to boot then.
It seems that this backtrace does not correspond to that log above. Crashes occur at different places; it's difficult to guess, what is going there.kdb:> bt
P.S.: Or you can try to boot 0.3.9 release, where atapi.sys was the default driver.
Re: ReactOS 0.3.10 on Industrial CPU board
It seem your onboard display are not supporting VESA 2.0, stay with 640x480 resolution (VGA). Re-install again from the BootCD and do not change the display resolution.Dinosaur wrote:Hi all
...
On board VGA and all other ...
The cd booted OK, and read all the files in a 640x480 screen, and then
switched screen mode, and locked up.
...
Currently, ReactOS only supported generic VGA (640x480) and SVGA/VESA (800x600 and above) driver.
Thank you for testing ReactOS.
Re: ReactOS 0.3.10 on Industrial CPU board
Hi all
Downloaded 0.3.9 from a third party site, couldnt find it anywhere on the ReactOS site.
This booted and copied files and allowed the installation onto
a CFC, then on completion asked for the reboot and removal of CD.
On reboot, the option menu showed various ReactOS options and when you select
any of these (including debug) it shows the icon (although in very poor resolution) and then
the dreaded blank screen again.
Tried the Copy/rename of atapi.sys to uniata.sys, but no avail.
What is needed to get ReactOS to recognise the full screen resolution ?
If I cant get 1024x768 in the long term, it is not worth proceeding.
I have a cd which has drivers for this board, from NT40 to XP, but ofcourse I cant use the installation program
cause I cant see anything. Is it NT40 we are looking for ? if so some of the file names are
S3DISPLY.DLL , NBICDNT.DLL, S3GAMMA2.DLL, S3INFO2.DLL , S3NB.DLL
TW5333.INF , S3NBM.SYS
Should one of these replace drivers supplied with ReactOS ?
Regards
Downloaded 0.3.9 from a third party site, couldnt find it anywhere on the ReactOS site.
This booted and copied files and allowed the installation onto
a CFC, then on completion asked for the reboot and removal of CD.
On reboot, the option menu showed various ReactOS options and when you select
any of these (including debug) it shows the icon (although in very poor resolution) and then
the dreaded blank screen again.
Tried the Copy/rename of atapi.sys to uniata.sys, but no avail.
What is needed to get ReactOS to recognise the full screen resolution ?
If I cant get 1024x768 in the long term, it is not worth proceeding.
I have a cd which has drivers for this board, from NT40 to XP, but ofcourse I cant use the installation program
cause I cant see anything. Is it NT40 we are looking for ? if so some of the file names are
S3DISPLY.DLL , NBICDNT.DLL, S3GAMMA2.DLL, S3INFO2.DLL , S3NB.DLL
TW5333.INF , S3NBM.SYS
Should one of these replace drivers supplied with ReactOS ?
Regards
Something interesting in the log?Dinosaur wrote: and then the dreaded blank screen again.
Crash again? What debug log says?Tried the Copy/rename of atapi.sys to uniata.sys, but no avail.
ReactOS' vbemp.sys driver supports 1024x768 and higher resolutions, only cannot change frequency — 60 Hz does not look good on a CRT display.If I cant get 1024x768 in the long term, it is not worth proceeding.
More likely, Windows 2000 or XP.Is it NT40 we are looking for ?
You can try to put .SYS file into ReactOS\system32\drivers\ directory, .INF file into ReactOS\inf\ and rename / remove vbemp.sys and vgamp.sys files. But compatibility with Windows drivers is still poor…Should one of these replace drivers supplied with ReactOS ?
Re: ReactOS 0.3.10 on Industrial CPU board
How much memory was assigned to the VGA? If possible reduce to 8MB or less. For high resolution display output, ReactOS 0.3.9 and above use minimum memory about 100MB. Your PC seem had default 128MB memory with onboard VGA sharing the memory. The other option is to add another 64MB or 128MB memory into PC100/133Mhz slot.
Thank you for testing ReactOS.
Thank you for testing ReactOS.
Who is online
Users browsing this forum: No registered users and 39 guests