Questions - Booting and Driver updates.

Ask your support questions in here

Moderator: Moderator Team

oldman
Posts: 1139
Joined: Sun Dec 20, 2009 1:23 pm

Questions - Booting and Driver updates.

Post by oldman »

Question 1 - Booting error.

I have an old FUJITSU ErgoPro, which has an Intel Pentium 2 (233Mhz) processor, 96Mb ram, 3.2Gb hard drive. The BIOS does not boot from CD/DVD drives, so I use a boot manager on a floppy. But every time I do a fresh install on this computer, it will not boot ReactOS and gives this BIOS error message:

"read error while reading drive"

Now if I do a 'fdisk /mbr' from a dos floppy, and re-start the computer, it then boots every time.

Can anyone give a reason why this should be?


Question 2 - Driver updates.

I have tried to use 'Device Manager - Properties - Driver - Update Driver', to install OEM drivers (Realtek 8139C network - S3 Virge DX video), but the 'Update Driver' button does not seem to work!

Is this un-implemented?
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

User avatar
gonzoMD
Posts: 1056
Joined: Fri Oct 20, 2006 7:49 am
Location: Germany
Contact:

Re: Questions - Booting and Driver updates.

Post by gonzoMD »

#1. I have no clue. Do you use Plop Bootmanager? if yes, maybe this page is interresting for the devs: http://www.plop.at/en/bootmanagers.html

#2. Yes, it is unimplemented. (IMO the button should be grayed out as long as it has no function)

edit: to install drivers which don't have a setup.exe, you should slipstream them to the installation iso, then they will maybe installed at setup. (you have to unpack all the .inf .sys and so on files)

User avatar
EmuandCo
Developer
Posts: 4439
Joined: Sun Nov 28, 2004 7:52 pm
Location: Germany, Bavaria, Steinfeld
Contact:

Re: Questions - Booting and Driver updates.

Post by EmuandCo »

Seems like the MBR is not installed on 1st stage setup. Does it have a serial Port? A log file would be very interesting.
ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.

oldman
Posts: 1139
Joined: Sun Dec 20, 2009 1:23 pm

Re: Questions - Booting and Driver updates.

Post by oldman »

gonzoMD wrote:#1. I have no clue. Do you use Plop Bootmanager? if yes, maybe this page is interresting for the devs: http://www.plop.at/en/bootmanagers.html
I use Smart BootManager http://sourceforge.net/projects/btmgr/
gonzoMD wrote:#2. Yes, it is unimplemented. (IMO the button should be grayed out as long as it has no function)

edit: to install drivers which don't have a setup.exe, you should slipstream them to the installation iso, then they will maybe installed at setup. (you have to unpack all the .inf .sys and so on files)
That's OK if it's not implemented, the vesa driver is good enough for the video and Ros comes with the RTL8139 driver.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

oldman
Posts: 1139
Joined: Sun Dec 20, 2009 1:23 pm

Re: Questions - Booting and Driver updates.

Post by oldman »

EmuandCo wrote:Seems like the MBR is not installed on 1st stage setup. Does it have a serial Port? A log file would be very interesting.
Here is a debug log.

Code: Select all

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.05.02 14:25:34 =~=~=~=~=~=~=~=~=~=~=~=
(ntoskrnl/kd/kdio.c:376) -----------------------------------------------------
(ntoskrnl/kd/kdio.c:377) ReactOS 0.4-SVN (Build 20140420-r62832)
(ntoskrnl/kd/kdio.c:379) 1 System Processor [95 MB Memory]
(ntoskrnl/kd/kdio.c:380) Command Line: NOGUIBOOT KDSERIAL DEBUGPORT=COM1 FIRSTCHANCE
(ntoskrnl/kd/kdio.c:384) ARC Paths: multi(0)disk(0)cdrom(96) \ multi(0)disk(0)cdrom(96) \reactos\
(ntoskrnl/ke/i386/cpu.c:494) 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_FAST_SYSCALL        
(ntoskrnl/ke/i386/cpu.c:801) Prefetch Cache: 32 bytes	L2 Cache: 524288 bytes	L2 Cache Line: 64 bytes	L2 Cache Associativity: 4
(ntoskrnl/mm/mminit.c:260)           0x80000000 - 0x83000000	Boot Loaded Image
(ntoskrnl/mm/mminit.c:264)           0xB0000000 - 0xB00A9000	PFN Database
(ntoskrnl/mm/mminit.c:268)           0xB00A9000 - 0xB02A9000	ARM3 Non Paged Pool
(ntoskrnl/mm/mminit.c:272)           0xB9400000 - 0xBB400000	System View Space
(ntoskrnl/mm/mminit.c:276)           0xBB400000 - 0xC0000000	Session Space
(ntoskrnl/mm/mminit.c:279)           0xC0000000 - 0xC03FFFFF	Page Tables
(ntoskrnl/mm/mminit.c:282)           0xC0300000 - 0xC0300FFF	Page Directories
(ntoskrnl/mm/mminit.c:285)           0xC0400000 - 0xC07FFFFF	Hyperspace
(ntoskrnl/mm/mminit.c:289)           0xE1000000 - 0xE5800000	ARM3 Paged Pool
(ntoskrnl/mm/mminit.c:292)           0xF8400000 - 0xFDBCD000	System PTE Space
(ntoskrnl/mm/mminit.c:295)           0xFDBCD000 - 0xFFBE0000	Non Paged Pool Expansion PTE Space
(ntoskrnl/config/cmhvlist.c:158) CmpAddToHiveFileList: Creation or opening of the hive list failed, status = c0000034
(hal/halx86/legacy/bussupp.c:594) Your machine has a PCI-to-PCI or CardBUS Bridge. PCI devices may fail!
(hal/halx86/legacy/bussupp.c:623) Found parent bus (indicating PCI Bridge). PCI devices may fail!

====== PCI BUS HARDWARE DETECTION =======

00:00.0 Host bridge [0600]:  Unknown device [8086:7180] (rev 03)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, medium devsel, latency 64
	Memory at 40000000 (32-bit, prefetchable) [size=1024M]

00:01.0 PCI bridge [0604]:  Unknown device [8086:7181] (rev 03)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, 66MHz, medium devsel, latency 64
	Memory at 40010100 (32-bit, non-prefetchable) [size=256]
	Memory at 22a000f0 (32-bit, non-prefetchable) [size=2M]
	Memory at 0000fff0 (32-bit, non-prefetchable) [size=256]
	Memory at 0000fff0 (32-bit, non-prefetchable) [size=256]

00:07.0 ISA bridge [0601]:  Unknown device [8086:7110] (rev 01)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, medium devsel, latency 0

00:07.1 IDE interface [0101]:  Unknown device [8086:7111] (rev 01)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, medium devsel, latency 64
	I/O ports at 8000 [size=32K]

00:07.2 USB controller [0c03]:  Unknown device [8086:7112] (rev 01)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, medium devsel, latency 64, IRQ 11
	I/O ports at 8020 [size=32]
	Device is using IRQ 11! ISA Cards using that IRQ may fail!
	Device is an Intel UHCI (USB) Controller. Turn off Legacy USB in your BIOS!

00:07.3 Secondary bus towards host CPU [0680]:  Unknown device [8086:7113] (rev 01)
	Subsystem: Unknown [0000:0000]
	Flags: medium devsel, latency 0

00:12.0 Ethernet controller [0200]:  Unknown device [10ec:8139] (rev 10)
	Subsystem: Unknown [10ec:8139]
	Flags: bus master, medium devsel, latency 64, IRQ 05
	I/O ports at 8400 [size=1K]
	Memory at 81000000 (32-bit, non-prefetchable) [size=16M]
	Device is using IRQ 5! ISA Cards using that IRQ may fail!

00:14.0 VGA compatible controller [0300]:  Unknown device [5333:8a01] (rev 01)
	Subsystem: Unknown [5333:8a01]
	Flags: bus master, medium devsel, latency 64, IRQ 10
	Memory at 84000000 (32-bit, non-prefetchable) [size=64M]
	Device is using IRQ 10! ISA Cards using that IRQ may fail!

====== PCI BUS DETECTION COMPLETE =======

PC Compatible Eisa/Isa HAL Detected
(ntoskrnl/io/pnpmgr/pnpinit.c:435) Need to build DACL
(ntoskrnl/io/pnpmgr/pnpmgr.c:3183) ZwOpenKey(\Registry\Machine\SYSTEM\CURRENTCONTROLSET\Control\Pnp) failed with status 0xc0000034
(ntoskrnl/io/pnpmgr/pnpmgr.c:3186) Firmware mapper is enabled
(ntoskrnl/io/pnpmgr/pnpreport.c:353) Reported device: DETECTEDInternal\PCI_HAL (Root\PCI_HAL\0)
SAC DriverEntry: Entering.
(ntoskrnl/io/iomgr/driver.c:1602) '\Driver\sacdrv' initialization failed, status (0xc0000037)
(ntoskrnl/io/iomgr/driver.c:61) Deleting driver object '\Driver\sacdrv'
(hal/halx86/legacy/bussupp.c:1159) Slot assignment for 5 on bus 0
(hal/halx86/legacy/bus/pcibus.c:715) 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!
(ntoskrnl/io/iomgr/driver.c:1602) '\Driver\buslogic' initialization failed, status (0xc00000c0)
(ntoskrnl/io/iomgr/driver.c:61) Deleting driver object '\Driver\buslogic'
(ntoskrnl/fstub/disksup.c:1709) FSTUB: MaxSector now = 1572480
(ntoskrnl/fstub/disksup.c:1709) FSTUB: MaxSector now = 1572480
(ntoskrnl/io/iomgr/arcname.c:386) Boot device found
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 1
(ntoskrnl/fstub/disksup.c:1709) FSTUB: MaxSector now = 1572480
Drive letter already used!
(ntoskrnl/ex/init.c:1959) Free non-cache pages: 549d
(base/setup/usetup/interface/devinst.c:95) Using driver 'pci.sys' for device 'PCI_HAL\PNP0A03\0'
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 'PCI_HAL\PNP0A03\0' (no FDO above)
(ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\pci.sys at FD866000 with b pages
(hal/halx86/legacy/halpnpdd.c:716) Start device received
(ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(base/setup/usetup/interface/devinst.c:95) Using driver 'i8042prt.sys' for device 'Root\*PNP0303\0000'
(base/setup/usetup/interface/devinst.c:147) Installing keyboard class driver for 'Root\*PNP0303\0000'
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 'Root\*PNP0303\0000' (no FDO above)
(ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\i8042prt.sys at FD856000 with 10 pages
(drivers/input/i8042prt/pnp.c:729) IRP_MJ_PNP / unknown minor function 0x9
(base/setup/usetup/interface/devinst.c:95) Using driver 'pci.sys' for device 'PCI\VEN_8086&DEV_7181&SUBSYS_00000000&REV_03\2&b3ac4ede&01'
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 'PCI\VEN_8086&DEV_7181&SUBSYS_00000000&REV_03\2&b3ac4ede&01' (no FDO above)
(drivers/bus/pci/pdo.c:1289) Enabling command flags for PCI device 0x1 on bus 0x0: None
(ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(base/setup/usetup/interface/devinst.c:95) Using driver 'pciide.sys' for device 'PCI\VEN_8086&DEV_7111&SUBSYS_00000000&REV_01\2&b3ac4ede&27'
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 'PCI\VEN_8086&DEV_7111&SUBSYS_00000000&REV_01\2&b3ac4ede&27' (no FDO above)
(ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\pciide.sys at FD84F000 with 7 pages
(ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\pciidex.sys at FD847000 with 8 pages
(hal/halx86/legacy/bus/pcibus.c:686) HAL: No PCI Resource Adjustment done! Hardware may malfunction
(drivers/bus/pci/pdo.c:1289) Enabling command flags for PCI device 0x27 on bus 0x0: [Bus master] [I/O space enable] 
(drivers/storage/ide/pciidex/fdo.c:467) IRP_MJ_PNP / Unknown minor function 0x9
(base/setup/usetup/interface/devinst.c:95) Using driver 'usbuhci.sys' for device 'PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01\2&b3ac4ede&47'
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 'PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01\2&b3ac4ede&47' (no FDO above)
(lib/drivers/libusb/libusb.cpp:33) USBLIB_AddDevice
(drivers/usb/usbuhci/hardware.cpp:169) CUSBHardwareDevice::Initialize
(hal/halx86/legacy/bus/pcibus.c:686) HAL: No PCI Resource Adjustment done! Hardware may malfunction
(drivers/bus/pci/pdo.c:1272) Assigning IRQ 11 to PCI device 0x47 on bus 0x0
(drivers/bus/pci/pdo.c:1289) Enabling command flags for PCI device 0x47 on bus 0x0: [Bus master] [I/O space enable] 
(drivers/usb/usbuhci/hardware.cpp:255) CUSBHardwareDevice::PnpStart
(drivers/usb/usbuhci/hardware.cpp:299) UHCI Base 00008020 Length ffff0020
(drivers/usb/usbuhci/hardware.cpp:607) [USBUHCI] InitializeController
(drivers/usb/usbuhci/hardware.cpp:635) [USBUHCI] LEGSUP 2000
(drivers/usb/usbuhci/hardware.cpp:640) [USBUHCI] Acquired ownership
(drivers/usb/usbuhci/hardware.cpp:643) [USBUHCI] SBRN 10
(drivers/usb/usbuhci/hardware.cpp:573) Waiting 10 milliseconds for global reset
(drivers/usb/usbuhci/hardware.cpp:734) Index 0 QueueHead FD844000 LinkPhysical 101022 ElementPhysical 1 PhysicalAddress 101000 Request 00000000 NextElementDescriptor 00000000
(drivers/usb/usbuhci/hardware.cpp:742) Index 1 QueueHead FD844020 LinkPhysical 101042 ElementPhysical 1 PhysicalAddress 101020 Request 00000000 NextElementDescriptor 00000000
(drivers/usb/usbuhci/hardware.cpp:751) Index 2 QueueHead FD844040 LinkPhysical 101062 ElementPhysical 1 PhysicalAddress 101040 Request 00000000 NextElementDescriptor 00000000
(drivers/usb/usbuhci/hardware.cpp:759) Index 3 QueueHead FD844060 LinkPhysical 101082 ElementPhysical 1 PhysicalAddress 101060 Request 00000000 NextElementDescriptor 00000000
(drivers/usb/usbuhci/hardware.cpp:767) Index 4 QueueHead FD844080 LinkPhysical 1 ElementPhysical 1 PhysicalAddress 101080 Request 00000000 NextElementDescriptor 00000000
(drivers/usb/usbuhci/hardware.cpp:834) [USBUHCI] Controller initialized
(drivers/usb/usbuhci/hardware.cpp:383) Starting Controller
(drivers/usb/usbuhci/hardware.cpp:472) [USBUHCI] USBCMD: 80 USBSTS 20
(drivers/usb/usbuhci/hardware.cpp:490) [USBUHCI] Status 0
(drivers/usb/usbuhci/hardware.cpp:501) [USBUHCI] USBCMD: 81 USBSTS 0
(drivers/usb/usbuhci/hardware.cpp:532) [USBUHCI] Controller Started
(drivers/usb/usbuhci/hardware.cpp:533) [USBUHCI] Controller Status 0
(drivers/usb/usbuhci/hardware.cpp:534) [USBUHCI] Controller Cmd Status c1
(drivers/usb/usbuhci/hardware.cpp:535) [USBUHCI] Controller Interrupt Status d
(drivers/usb/usbuhci/hardware.cpp:536) [USBUHCI] Controller Frame 24
(drivers/usb/usbuhci/hardware.cpp:537) [USBUHCI] Controller Port Status 0 80
(drivers/usb/usbuhci/hardware.cpp:538) [USBUHCI] Controller Port Status 1 80
(ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(lib/drivers/libusb/hub_controller.cpp:3922) CHubController::CreatePDO: DeviceName \Device\USBPDO-0
(base/setup/usetup/interface/devinst.c:95) Using driver 'uniata.sys' for device 'PCIIDE\IDEChannel\3&ae0498c8&0'
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 'PCIIDE\IDEChannel\3&ae0498c8&0' (no FDO above)
(base/setup/usetup/interface/devinst.c:95) Using driver 'uniata.sys' for device 'PCIIDE\IDEChannel\3&ae0498c8&1'
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 'PCIIDE\IDEChannel\3&ae0498c8&1' (no FDO above)
(base/setup/usetup/interface/devinst.c:95) Using driver 'usbhub.sys' for device 'USB\ROOT_HUB\3&c2d91217'
(ntoskrnl/io/pnpmgr/plugplay.c:635) A new driver will be loaded for 'USB\ROOT_HUB\3&c2d91217' (no FDO above)
(drivers/usb/usbhub/fdo.c:1641) Status 0, Result 0x00000040
(drivers/usb/usbhub/fdo.c:1642) InformationLevel 0
(drivers/usb/usbhub/fdo.c:1643) ActualLength 40
(drivers/usb/usbhub/fdo.c:1644) PortNumber 0
(drivers/usb/usbhub/fdo.c:1645) DeviceDescriptor 20000112
(drivers/usb/usbhub/fdo.c:1646) HubAddress 0
(drivers/usb/usbhub/fdo.c:1647) NumberofPipes 0
(drivers/usb/usbhub/fdo.c:1740) HubDeviceExtension->UsbExtHubInfo.NumberOfPorts 2
(drivers/usb/usbuhci/hardware.cpp:1161) [UHCI] SetPortFeature PortId 0 Feature 8
(drivers/usb/usbuhci/hardware.cpp:1161) [UHCI] SetPortFeature PortId 1 Feature 8
(lib/drivers/libusb/hub_controller.cpp:314) [USBUHCI] SCE Request B0257C48 TransferBufferLength 8 Flags 3 MDL 00000000
(lib/drivers/libusb/hub_controller.cpp:325) [USBUHCI] Port 0: Status 100, Change 0
(lib/drivers/libusb/hub_controller.cpp:325) [USBUHCI] Port 1: Status 100, Change 0
(ntoskrnl/io/pnpmgr/pnpmgr.c:4028) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(ntoskrnl/ex/init.c:2001) Free non-cache pages: 53d6
(ntoskrnl/mm/ARM3/zeropage.c:50) Free non-cache pages: 55fa
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 1
(ntoskrnl/fstub/disksup.c:1709) FSTUB: MaxSector now = 1572480
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 1017f
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 11f
(lib/fslib/vfatlib/vfatlib.c:210) WARNING: Failed to lock volume for formatting! Format may fail! (Status: 0xc0000010)
(lib/fslib/vfatlib/vfatlib.c:266) Failed to unlock volume (Status: 0xc0000010)
(base/setup/usetup/interface/usetup.c:3127) CHECKPOINT:HALF_COPIED
Boot took 35081699867 cycles!
Interrupts: 17513 System Calls: 21619 Context Switches: 7851
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 1017f
(ntoskrnl/config/cmlazy.c:81) Flushing: \Device\Harddisk0\Partition1\ReactOS\System32\Config\SECURITY
(ntoskrnl/config/cmlazy.c:82) Handle: 800000F8
WARNING:  HvpWriteLog at lib/cmlib/hivewrt.c:26 is UNIMPLEMENTED!
(ntoskrnl/config/cmlazy.c:81) Flushing: \Device\Harddisk0\Partition1\ReactOS\System32\Config\SOFTWARE
(ntoskrnl/config/cmlazy.c:82) Handle: 80000158
WARNING:  HvpWriteLog at lib/cmlib/hivewrt.c:26 is UNIMPLEMENTED!
(ntoskrnl/config/cmlazy.c:81) Flushing: \Device\Harddisk0\Partition1\ReactOS\System32\Config\DEFAULT
(ntoskrnl/config/cmlazy.c:82) Handle: 80000148
WARNING:  HvpWriteLog at lib/cmlib/hivewrt.c:26 is UNIMPLEMENTED!
(ntoskrnl/config/cmlazy.c:81) Flushing: \Device\Harddisk0\Partition1\ReactOS\System32\Config\SAM
(ntoskrnl/config/cmlazy.c:82) Handle: 8000013C
WARNING:  HvpWriteLog at lib/cmlib/hivewrt.c:26 is UNIMPLEMENTED!
(ntoskrnl/config/cmlazy.c:81) Flushing: \SystemRoot\System32\Config\SYSTEM
(ntoskrnl/config/cmlazy.c:82) Handle: 80000144
WARNING:  HvpWriteLog at lib/cmlib/hivewrt.c:26 is UNIMPLEMENTED!
(base/setup/usetup/bootsup.c:2243) No or unknown boot loader found
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 9
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 9
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 116
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 9
(ntoskrnl/io/iomgr/file.c:438) Using IopParseDevice() hack. Requested invalid attributes: 116
[7h[18t
Entered debugger on embedded INT3 at 0x0008:0x809578b2.
[18tkdb:> [18t
[18tkdb:> 
I tried to get a back trace, but having entered the debugger, it would not accept any more keyboard inputs.
To re-boot I have had to use the computer's on/off button. When it re-booted, I got the "read error while reading drive" message, so I did the 'fdisk /mbr' and re-booted, which gave this error message "freeldr.sys not found".

I opened the debug log using a unix text editor and I see it puts some extra text in, such as "[18t" before and after kbd:>

If there is something in the debug log that makes it worth a Jira issue, then I will get another debug log for making a boot floppy, which also fails to boot.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

Forever Winter
Posts: 131
Joined: Sun Oct 20, 2013 6:50 am

Re: Questions - Booting and Driver updates.

Post by Forever Winter »

@oldman

Sure that the BIOS displays this message? ReactOS MBR code throws this if one of the involved INT 13 functions return with the carry flag set.

Has this computer a Phoenix BIOS?

oldman
Posts: 1139
Joined: Sun Dec 20, 2009 1:23 pm

Re: Questions - Booting and Driver updates.

Post by oldman »

Forever Winter wrote:@oldman

Sure that the BIOS displays this message? ReactOS MBR code throws this if one of the involved INT 13 functions return with the carry flag set.
This is the error message that it gives "read error while reading drive" until I do a 'fdisk /mbr'.
Forever Winter wrote: Has this computer a Phoenix BIOS?
It has it's own FUJITSU BIOS.
I have copied the mbr to a file and this is what it looks like in a text editor:
úü1ÀŽÐŽØ½ BEFORE.TXT (before doing a 'fdisk /mbr')
3ÀŽÐ¼ AFTER.TXT (after doing a 'fdisk /mbr')
They can be down-loaded from here:
http://sites.google.com/site/em7575w/ho ... BEFORE.TXT
http://sites.google.com/site/em7575w/ho ... /AFTER.TXT

But note: I have no such problems with another old computer, which is very much newer than the FUJITSU.

I have even done a fdisk /mbr on the newer one and it still boots, with or without doing the 'fdisk /mbr'.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

Forever Winter
Posts: 131
Joined: Sun Oct 20, 2013 6:50 am

Re: Questions - Booting and Driver updates.

Post by Forever Winter »

@oldman

Ok, I guess if you put the Fujitsu harddisk in the PC that works, install ReactOS (but without rewriting the MBR with FDISK) and than put it back in the Fujitsu, you get the same error?

oldman
Posts: 1139
Joined: Sun Dec 20, 2009 1:23 pm

Re: Questions - Booting and Driver updates.

Post by oldman »

Forever Winter wrote:@oldman
Ok, I guess if you put the Fujitsu harddisk in the PC that works, install ReactOS (but without rewriting the MBR with FDISK) and than put it back in the Fujitsu, you get the same error?
I will not be doing that, because the hard drive is clad with padding, so it would be hard to remove.

The mbr dump code looks the same viewed in a test editor for both computers. There is much more info when viewed in an hex editor.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

Forever Winter
Posts: 131
Joined: Sun Oct 20, 2013 6:50 am

Re: Questions - Booting and Driver updates.

Post by Forever Winter »

@oldman

No Problem. Since it works after fdisk, I think it is not a problem with the harddisk.
Ok, are you able to build ReactOS from the source code?

oldman
Posts: 1139
Joined: Sun Dec 20, 2009 1:23 pm

Re: Questions - Booting and Driver updates.

Post by oldman »

Forever Winter wrote:@oldman
Ok, are you able to build ReactOS from the source code?
I have never compiled ReactOS and I have very little experience of compiling, full stop. I have done some compiling years ago with Linux, but not much.

Are you going to suggest that I compile Ros on this Fujitsu? There is only 96Mb of ram, and it only has a 233Mhz processor.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

User avatar
EmuandCo
Developer
Posts: 4439
Joined: Sun Nov 28, 2004 7:52 pm
Location: Germany, Bavaria, Steinfeld
Contact:

Re: Questions - Booting and Driver updates.

Post by EmuandCo »

Forever Winter wrote:@oldman

No Problem. Since it works after fdisk, I think it is not a problem with the harddisk.
Ok, are you able to build ReactOS from the source code?
ROS already has Debugging active on 1st stage, so what do you wanna suggest him?

You could enable more debugging on fastfat, but the problem should be somewhere else.
ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.

Forever Winter
Posts: 131
Joined: Sun Oct 20, 2013 6:50 am

Re: Questions - Booting and Driver updates.

Post by Forever Winter »

@oldman

Of course not. I have asked because I don't know how far your experience goes in this direction and it may help to find the reason for the error.
I hope I don't made you angry with that.

@EmuandCo

Thats true, the problem seems to be somewhere else.
As said, the MBR code throws this error message, if an INT 13 call returns with carry flag set, so I would start to search there for possible problems.

As far as I know, at least some versions of DOS record the original BIOS drive number in the MBR (or uses the active flag or whatsoever),
and use the stored value instead the one the BIOS gives. Because the DOS code works, I would first suggest him to try to load DL on entry with the BIOS drive number of the harddisk he has installed ReactOS
on, to force the code to use this drive and not the BIOS supplied value and see if it works.

oldman
Posts: 1139
Joined: Sun Dec 20, 2009 1:23 pm

Re: Questions - Booting and Driver updates.

Post by oldman »

Forever Winter wrote:@oldman

Of course not. I have asked because I don't know how far your experience goes in this direction and it may help to find the reason for the error.
I hope I don't made you angry with that.
No, that would never make me angry! I was even prepared to have a go at compiling. So don't worry, you have not offended me.
Forever Winter wrote: As far as I know, at least some versions of DOS record the original BIOS drive number in the MBR (or uses the active flag or whatsoever),
and use the stored value instead the one the BIOS gives. Because the DOS code works, I would first suggest him to try to load DL on entry with the BIOS drive number of the harddisk he has installed ReactOS
on, to force the code to use this drive and not the BIOS supplied value and see if it works.
If this was aimed at me, then I need you to explain in much more detail, what it is that you want me to do.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

Forever Winter
Posts: 131
Joined: Sun Oct 20, 2013 6:50 am

Re: Questions - Booting and Driver updates.

Post by Forever Winter »

@oldman

The part that needs to be changed is the code in dosmbr.s, wich is located in <path_to_source_code>\boot\freeldr\bootsect and contains the source for the mbr code.
The change needed contains of inserting a "mov dl, <drive>" (without the quotes) before the first int13 call is made, where <drive> is the drive number in the sheme
expected by the int13 interface. Floppies and such are in the range 0 - 127 and harddisks and such go from 128 - 255. So if you have installed ReactOS on the first
harddrive, it should be 128 for example.

So if you insert it near the entry point, wich looks like

.code16
real_start:
cli
cld
xor ax, ax
mov ss, ax // initialize stack
...

and you install ROS on the first harddisk, it should then look like

.code16
real_start:
cli
cld
mov dl, 128
xor ax, ax
mov ss, ax // initialize stack
...

You can than save the changes and rebuild it with ninja dosmbr and than build an iso image with ninja bootcd.
You can now burn the generated image to a CD/CD-RW or whatsoever and install using it.
If the error is thrown because your BIOS supplies a wrong boot drive number or supply it in an other sheme as the one
expected by the int13 interface and you have installed ROS on the disk number given in the MOV statement, the
error message should now disapear.

Post Reply

Who is online

Users browsing this forum: Yandex [Bot] and 0 guests