I'm a Linux-Ubuntu Based System and Windows 7 user. This is the first time I'm trying ReactOS. First I messed with it on VirtualBox 6.1, and then I found out through the wiki that I'm told to use 5.2.38. Since VitrualBox 6.1 is installed on my main Linux Mint 18.3 system I didn't go any farther with ReactOS in VirtualBox. I have a game that I wanted to try on ReactOS. Since I decided not to try it in VirtualBox, I moved to real hardware. The Installer behaved just like the Windows XP installer. However, after I partitioned and formatted the hard drive, the installer began scanning the hardware but wouldn't go anywhere. It seemed to just freeze up. Is there anything I can try? BTW: I tested the LiveCD and it booted up ok.
Questions:
1. What version of ReactOS are you trying to install?
2. What partition are you trying to install to?
3. What file system is the partition formatted to?
Suggestions:
1. Install to the first partition.
2. Use only a partition formatted FAT32 or Btrfs.
3. Try installing several times before giving up.
4. If you have only tried the 0.4.13 release ISO, then try one of the latest trunk builds.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Right now I just want to focus on the Dell Vostro 400 computer.
I have the installer CD put in. Version is 0.4.13. It doesn't go past: "Please wait while the ReactOS Setup initializes itself and discovers your devices" It's been sitting that way for a half hour! However the Live version 0.4.13 does work.
I've tried:
reactos-livecd-0.4.15-dev-382-g3cb8ee6-x86-gcc-lin-dbg: It runs.
reactos-bootcd-0.4.15-dev-382-g3cb8ee6-x86-gcc-lin-dbg freezes up on "Please wait while the ReactOS Setup initializes itself and discovers your devices"
Last edited by ReactUser204 on Sun Jun 14, 2020 6:05 pm, edited 1 time in total.
From what you describe, ReactOS is loaded into memory and fails at the first blue screen, so it is possible to get debug information. Assuming that you have not got a serial port, then you will have to alter txtsetup.sif (the instructions are in How to get a debug log) to get debug information shown on the screen. You can then take a photo of the screen, which should show where it is failing. You may need to create a Jira issue (bug report) if it is not a known problem, see this guide for how to do it.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
oldman wrote: ↑Mon Jun 15, 2020 10:33 am
From what you describe, ReactOS is loaded into memory and fails at the first blue screen, so it is possible to get debug information. Assuming that you have not got a serial port, then you will have to alter txtsetup.sif (the instructions are in How to get a debug log) to get debug information shown on the screen.
I don't know how to do this:
I tried to edit txtsetup.sif inside the iso file. I tried to extract it, and then sudo into a text editor, edit the lines, and then put the file back into the iso file. After burning a new cd, and testing. It doesn't work.
The instructions oldman linked are for when you're building ReactOS yourself from source. I've never had luck attempting to edit a pre-made ISO, but I've heard that it's possible with certain tools.
ReactUser204 wrote: ↑Mon Jun 15, 2020 5:17 pm I don't know how to do this:
I tried to edit txtsetup.sif inside the iso file. I tried to extract it, and then sudo into a text editor, edit the lines, and then put the file back into the iso file. After burning a new cd, and testing. It doesn't work.
If you use the software that I have tested, it should boot and show debug info on the screen; it worked for me.
What you will see, is the usual bar telling you what is loading. After it has loaded the drivers, you will then see the debug info before it comes to the screen Initializes itself and discovers your hardware, where you said that it froze .
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
ReactUser204 wrote: ↑Wed Jun 17, 2020 2:20 am
If you still want a picture, I'll try to take one. But I can type out what it says at the bottom.
I don't want a photo because I am not a developer, but the photo will be needed if you create a Jira issue.
ReactUser204 wrote: ↑Wed Jun 17, 2020 2:20 am
Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault)
Memory at 0x42202D20 could not be read: Page not present .
kdb:>
The debug info that is required, are the lines above what you have shown here. So, without a photo of the whole screen, you will have a lot of typing to do.
The developers need to see what caused the exception.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
ReactUser204 wrote: ↑Wed Jun 17, 2020 2:20 am
If you still want a picture, I'll try to take one. But I can type out what it says at the bottom.
I don't want a photo because I am not a developer, but the photo will be needed if you create a Jira issue.
ReactUser204 wrote: ↑Wed Jun 17, 2020 2:20 am
Entered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault)
Memory at 0x42202D20 could not be read: Page not present .
kdb:>
The debug info that is required, are the lines above what you have shown here. So, without a photo of the whole screen, you will have a lot of typing to do.
The developers need to see what caused the exception.
I do not know how to send them a picture of it. Most people use smartphones to take pictures. I do not own one of those. I will need to try to use my old Kodak Easy Share C433. Also some websites allow you to directly upload pictures. Others force you to use a picture hosting site. For years I used photobucket for this kind of thing. Then photobucket changed their rules, and I decided enough of them. Then I did some research and found an open source alternative that I felt comfortable with. Then after about year or two, that site closed down. I have thought about imgur but I don't like to support them. I don't use facebook or instagram either. I don't know how to get a picture over to them.
Imgur seems fine but the externally hosted images will not display here. Instead you can attach an image here using the attachment tool, no need to use imgur any more at least on this forum.
Skillset: VMS,DOS,Windows Sysadmin from 1985, fault-tolerance, VaxCluster, Alpha,Sparc. DCL,QB,VBDOS- VB6,.NET, PHP,NODE.JS, Graphic Design, Project Manager, CMS, Quad Electronics. classic cars & m'bikes. Artist in water & oils. Historian.
dizt3mp3r wrote: ↑Thu Jun 18, 2020 10:36 am
There is a lot you don't know
Imgur seems fine but the externally hosted images will not display here. Instead you can attach an image here using the attachment tool, no need to use imgur any more at least on this forum.
I'm writing this "Full Editor & Preview" mode. There does not seem to be an attachment tool on my end.
Last edited by ReactUser204 on Thu Jun 18, 2020 6:29 pm, edited 2 times in total.
ReactUser204 wrote: ↑Thu Jun 18, 2020 6:27 pm
I'm writing this "Full Editor & Preview" mode. There does not seem to be an attachment tool on my end.
Look outside of the editor and below, you should see Options tab and Attachments tab, click on attachments and you will see an Add files button.
Please keep the Windows classic 9x/2000 look and feel.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.