I'm re setting up my ROS dev environment, after a format/reinstall, and i'm encountering the following problem under both QEMU and ReactOS:
While booting from the livecd or the bootcd i get an inaccessible boot device error. The HD partition on VMWare is a FAT32 partition formatted in win98, the partition in QEMU is an unformatted partition.
Any idea on how to fix this?
Here is debug from the livecd, can't get anything from the bootcd though, since it doesn't use freeldr not sure how to change the debug port
Richard Campbell wrote:
I'm re setting up my ROS dev environment, after a format/reinstall, and i'm encountering the following problem under both QEMU and ReactOS:
While booting from the livecd or the bootcd i get an inaccessible boot device error. The HD partition on VMWare is a FAT32 partition formatted in win98, the partition in QEMU is an unformatted partition.
Any idea on how to fix this? _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Used memory 65536Kb (mm/virtual.c:230) FIXME: MEMORY_AREA_SYSTEM case incomplete (or possibly wrong) for NtQueryVirtualMemory() DriverBase for \SystemRoot\system32\drivers\pci.sys: dcb44000 Peripheral Component Interconnect Bus Driver DriverBase for acpi.sys: dcb4d000 Advanced Configuration and Power Interface Bus Driver ACPI: System firmware supports: +------------------------------------------------------------ | Sx states: +S0 -S1 -S2 -S3 -S4 +S5 +------------------------------------------------------------ Sleep Button: found DriverBase for scsiport.sys: dcb83000 DriverBase for atapi.sys: dcb8e000 (ldr/loader.c:1478) LdrPEGetExportByName(): failed to find NTOSKRNL.RtlConvertUlongToLargeInteger (ldr/loader.c:1563) Failed to import NTOSKRNL.RtlConvertUlongToLargeInteger from scsiport.sys DriverBase for class2.sys: dcb98000 DriverBase for cdrom.sys: dcba1000 DriverBase for disk.sys: dcba8000 DriverBase for vfatfs.sys: dcbb0000 DriverBase for bootvid.sys: dcbc5000 DriverBase for cdfs.sys: dcbe5000 DriverBase for ndis.sys: dcbf0000 IoCreateSystemRootLink FAILED: (0xc0000001) - %KERNEL-WRN-UNSUCCESSFUL UNSUCCESSFUL KeBugCheck at ke/main.c:699 Bug detected (code 7b param 0 0 0 0) INACCESSIBLE_BOOT_DEVICE
Frames: <ntoskrnl.exe: b7f9> <ntoskrnl.exe: b819> <C008BAB8> <ntoskrnl.exe: d50c> <C008C374> <ntoskrnl.exe: 1140>
From: Richard Campbell
I'm re setting up my ROS dev environment, after a format/reinstall, and i'm encountering the following problem under both QEMU and ReactOS:
While booting from the livecd or the bootcd i get an inaccessible boot device error. The HD partition on VMWare is a FAT32 partition formatted in win98, the partition in QEMU is an unformatted partition.
Any idea on how to fix this?
You're probably using binutils 2.15.91. There's a bug in there that prevents ReactOS from booting. Revert to binutils 2.15.90.
Gé van Geldorp.
Ah yes, that's the problem:
GNU ld version 2.15.91 20040904
BTW as mingw 3.2 is going to include this, are we going to work around this or just recommend that users don't use binutils 2.15.90?
Ge van Geldorp wrote:
From: Richard Campbell
I'm re setting up my ROS dev environment, after a format/reinstall, and i'm encountering the following problem under both QEMU and ReactOS:
While booting from the livecd or the bootcd i get an inaccessible boot device error. The HD partition on VMWare is a FAT32 partition formatted in win98, the partition in QEMU is an unformatted partition.
Any idea on how to fix this?
You're probably using binutils 2.15.91. There's a bug in there that prevents ReactOS from booting. Revert to binutils 2.15.90.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
From: Richard Campbell
BTW as mingw 3.2 is going to include this, are we going to work around this or just recommend that users don't use binutils 2.15.90?
I assume you meant "don't use binutils 2.15.91".... Don't think there's a workaround so we'll have to tell people not to use that one. 2.15.90 is ok, so is current binutils CVS.
Gé van Geldorp.
Hi
I got a Directory with my version of Reactos i compare with the online SVN version But It where no problem with the CVN version because files where only changed when they where updated
Now this is everywhere
/* $Id: mdl.c 13036 2005-01-13 23:47:10Z blight $ *\
And the file isn�t changed at all� ? Is it because when u update u touches all of the files but only update one it bugs me a lot also because Reactos now fill 240 Mb. instead of 60 Mb. And it takes a compare tool a lot of time if it also shouldn�t care about the top..
I modified/added about a 10-14 MB of code myself and therefore it�s hard to se when it�s only the top theirs changed �The Version� and nothing more and can�t really see why updating the vesion and not the file itself their can be no logic reason for that
The latest update of tool This file llmosrt.c and some more caused large errors http://www.alumni.caltech.edu/~pje/ Because it tries to remove memory there are in use and it give me a lot of trouble when making the bootcd and livecd think some just update the files from the web page without thinking.. ?
Livecd Cant really use it because all files trying to write contents on the livecd and I think its really hard to fix so all the files get written on a local hard disk or in memory so why really have this could only use it for presentation or alike� you cant have apps running specially not when Reactos comes to and working state..
Thomas Larsen
__________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com
Sorry for the delay in replying. Time is lacking as of late. Where do i get binutils 2.15.90, i can't find it on mingw.org nor the sourceforge.net site.
Ge van Geldorp wrote:
From: Richard Campbell
BTW as mingw 3.2 is going to include this, are we going to work around this or just recommend that users don't use binutils 2.15.90?
I assume you meant "don't use binutils 2.15.91".... Don't think there's a workaround so we'll have to tell people not to use that one. 2.15.90 is ok, so is current binutils CVS.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
2.15.90 is no longer on the MingW website. MingW 3.1 comes with 2.13.90, which does not work correctly when compiling ROS.
Any idea where i can get a version that DOES work?
Richard
Richard Campbell wrote:
Sorry for the delay in replying. Time is lacking as of late. Where do i get binutils 2.15.90, i can't find it on mingw.org nor the sourceforge.net site.
Ge van Geldorp wrote:
From: Richard Campbell
BTW as mingw 3.2 is going to include this, are we going to work around this or just recommend that users don't use binutils 2.15.90?
I assume you meant "don't use binutils 2.15.91".... Don't think there's a workaround so we'll have to tell people not to use that one. 2.15.90 is ok, so is current binutils CVS.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
From: Richard Campbell
2.15.90 is no longer on the MingW website. MingW 3.1 comes with 2.13.90, which does not work correctly when compiling ROS.
Any idea where i can get a version that DOES work?
http://public.planetmirror.com/pub/sf/m/mi/mingw/binutils-2.15.90-20040222-1 .tar.gz
Hi,
have you checked this one: http://prdownloads.sf.net/mingw/binutils-2.13.90-20030111-1.tar.gz?download
I downloaded it correctly yet.
Regards Jirka
Richard Campbell napsal(a):
2.15.90 is no longer on the MingW website. MingW 3.1 comes with 2.13.90, which does not work correctly when compiling ROS.
Any idea where i can get a version that DOES work?
Richard
Richard Campbell wrote:
Sorry for the delay in replying. Time is lacking as of late. Where do i get binutils 2.15.90, i can't find it on mingw.org nor the sourceforge.net site.
Ge van Geldorp wrote:
From: Richard Campbell
BTW as mingw 3.2 is going to include this, are we going to work around this or just recommend that users don't use binutils 2.15.90?
I assume you meant "don't use binutils 2.15.91".... Don't think there's a workaround so we'll have to tell people not to use that one. 2.15.90 is ok, so is current binutils CVS.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
That is 2.13.90. It does not work. GvG posted a link above.
By the way i believe this should be posted on the developers page.
Jiri Doubek wrote:
Hi,
have you checked this one: http://prdownloads.sf.net/mingw/binutils-2.13.90-20030111-1.tar.gz?download
I downloaded it correctly yet.
Regards Jirka
Richard Campbell napsal(a):
2.15.90 is no longer on the MingW website. MingW 3.1 comes with 2.13.90, which does not work correctly when compiling ROS.
Any idea where i can get a version that DOES work?
Richard
Richard Campbell wrote:
Sorry for the delay in replying. Time is lacking as of late. Where do i get binutils 2.15.90, i can't find it on mingw.org nor the sourceforge.net site.
Ge van Geldorp wrote:
From: Richard Campbell
BTW as mingw 3.2 is going to include this, are we going to work around this or just recommend that users don't use binutils 2.15.90?
I assume you meant "don't use binutils 2.15.91".... Don't think there's a workaround so we'll have to tell people not to use that one. 2.15.90 is ok, so is current binutils CVS.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
From: Jiri Doubek
have you checked this one:
http://prdownloads.sf.net/mingw/binutils-2.13.90-20030111-1.tar.gz?download
I downloaded it correctly yet.
But that is 2.-->13<--.90 which had some problems too iirc. ReactOS needs 2.-->15<--.90
Please forgive my intrusion in this topic and speaking before knowing the complete details about your discussion. But I'd like to add that I downloaded the latest utilities to setup MinGW environment to compile ReactOS and everything works fine for me.
binutils : 2.15.91 gcc-* : 4.3.3-20040217-1 MinGW: 3.1.0-1 W32api : 3.5
Ge van Geldorp wrote:
From: Jiri Doubek
have you checked this one:
http://prdownloads.sf.net/mingw/binutils-2.13.90-20030111-1.tar.gz?download
I downloaded it correctly yet.
But that is 2.-->13<--.90 which had some problems too iirc. ReactOS needs 2.-->15<--.90
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
From: AzeemArif
Please forgive my intrusion in this topic and speaking before knowing the complete details about your discussion. But I'd like to add that I downloaded the latest utilities to setup MinGW environment to compile ReactOS and everything works fine for me.
binutils : 2.15.91 gcc-* : 4.3.3-20040217-1 MinGW: 3.1.0-1 W32api : 3.5
But have you tried to boot from the resulting .iso image? There are a lot of reports that it fails with INACCESSIBLE_BOOT_DEVICE when you use binutils 2.15.91.
Gé van Geldorp.
Ge van Geldorp wrote:
From: AzeemArif
Please forgive my intrusion in this topic and speaking before knowing the complete details about your discussion. But I'd like to add that I downloaded the latest utilities to setup MinGW environment to compile ReactOS and everything works fine for me.
binutils : 2.15.91 gcc-* : 4.3.3-20040217-1 MinGW: 3.1.0-1 W32api : 3.5
But have you tried to boot from the resulting .iso image? There are a lot of reports that it fails with INACCESSIBLE_BOOT_DEVICE when you use binutils 2.15.91.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
You are right.
Currently I am debugging and asking people on the forum about "
INACCESSIBLE_BOOT_DEVICE" problem. I did not know it was because of toolchain.
When I said "everything is fine" in my last mail, I meant "compilation".
Sorry for wasting your time
GCC 3.4.2 Binutils 2.15.90
are my versions. Seems to be a bug in windres
Ge van Geldorp wrote:
From: AzeemArif
Please forgive my intrusion in this topic and speaking before knowing the complete details about your discussion. But I'd like to add that I downloaded the latest utilities to setup MinGW environment to compile ReactOS and everything works fine for me.
binutils : 2.15.91 gcc-* : 4.3.3-20040217-1 MinGW: 3.1.0-1 W32api : 3.5
But have you tried to boot from the resulting .iso image? There are a lot of reports that it fails with INACCESSIBLE_BOOT_DEVICE when you use binutils 2.15.91.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Sorry,
I thought you weren't able to download 2.13.90, not 2.15.90. But as I said I just downloaded these binutils and they work for me good.
Regards Jirka
Richard Campbell napsal(a):
2.15.90 is no longer on the MingW website. MingW 3.1 comes with 2.13.90, which does not work correctly when compiling ROS.
Any idea where i can get a version that DOES work?
Richard
Richard Campbell wrote:
Sorry for the delay in replying. Time is lacking as of late. Where do i get binutils 2.15.90, i can't find it on mingw.org nor the sourceforge.net site.
Ge van Geldorp wrote:
From: Richard Campbell
BTW as mingw 3.2 is going to include this, are we going to work around this or just recommend that users don't use binutils 2.15.90?
I assume you meant "don't use binutils 2.15.91".... Don't think there's a workaround so we'll have to tell people not to use that one. 2.15.90 is ok, so is current binutils CVS.
Gé van Geldorp.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev