If I'm supposed to keep following, you're going to have to not make me skip over 2 pages of unrelated stuff every day.
Looking at the messages that are just scrolling by will indeed not be particularly helpful. From your earlier messages it sounded like the LiveCD also failed to boot, so I hoped we would see it crash/hang. If the LiveCD boots successfully, we'll have to investigate using the BootCD.
The following patch enables screen debugging:
ThFabba wrote:If I'm supposed to keep following, you're going to have to not make me skip over 2 pages of unrelated stuff every day.
Looking at the messages that are just scrolling by will indeed not be particularly helpful. From your earlier messages it sounded like the LiveCD also failed to boot, so I hoped we would see it crash/hang. If the LiveCD boots successfully, we'll have to investigate using the BootCD.
The following patch enables screen debugging:
ThFabba wrote:If I'm supposed to keep following, you're going to have to not make me skip over 2 pages of unrelated stuff every day.
Looking at the messages that are just scrolling by will indeed not be particularly helpful. From your earlier messages it sounded like the LiveCD also failed to boot, so I hoped we would see it crash/hang. If the LiveCD boots successfully, we'll have to investigate using the BootCD.
The following patch enables screen debugging:
Right, I tried the iso and the process showed lots of lines of code ; it ends with "kdb: >" and that's all, nothing happens after that ; should I film the whole process like last time and post the video ?
phoenix63 wrote:
Right, I tried the iso and the process showed lots of lines of code ; it ends with "kdb: >" and that's all, nothing happens after that ; should I film the whole process like last time and post the video ?
Can you take a photo of the screen when it reaches the kdb> prompt. When you have taken the photo, type bt and then press the Enter key; if possible, video it and when it stops again take another photo.
The bt command will give developers more info. bt stands for back trace.
Then you will have to wait for ThFabba or you could join the irc from the front page and try contacting him there.
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.
Very good so far, but some info as been lost. I see that you have been presented with the option press q to abort, any other key to continue.
To get maximum debug output, you needed to take a photo when it stopped at that option, then take another photo when it stopped at the kdb> prompt.
If it is not too much trouble (for the sake of a full debug output), could you do another run and every time it stops take a photo.
Some times that option appears several times; I believe I have seen it happen as much as 3 times in the past.
I find the photos are easy to see the text, but the video is a little blurred.
I hope they fix the bug for you and for everyone else.
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.
OK I'll do that, but just for info, when I got the "press q to abort, any other key to continue." message, nothing else was shown ; then I pressed a key to continue and I code the lines you can see till the kdb> prompt. Si I don't think any info was lost.
The process stopped only once, when I got the "press q to abort, any other key to continue." message.
Sorry about the video, I'm not a marksman, which is annoying really since I have quite a good camera (filmed in 1080p too) It looked OK on my side but I agree it could be better.
in KDB it maybe able to get past the error. If it doesn't then well that was a try. and you should take a pic before you pressed enter on the continue message because some data was cut off.
cont is short for continue. So when you type cont it will try to continue to run
ReactOS Donator ~ $5.00 | Linux Mint Donator ~ $1.00 in BTC
in KDB it maybe able to get past the error. If it doesn't then well that was a try. and you should take a pic before you pressed enter on the continue message because some data was cut off.
cont is short for continue. So when you type cont it will try to continue to run
I assure you no data was cut off After the message "press q to abort, any other key to continue.", there was absolutely no data written ; the rest appeared after I hit a key
But as I said, I'll do it again, promise
Now, I have a question about your request : when should I type
The "missing" data we're looking for is everything between "kdb:> bt" and "<usbuhci.sys:6344>". The "Press q to abort" should interrupt printing at just the right point to be able to see those lines.
Thanks.
ThFabba wrote:The "missing" data we're looking for is everything between "kdb:> bt" and "<usbuhci.sys:6344>". The "Press q to abort" should interrupt printing at just the right point to be able to see those lines.
Thanks.
... it looks like it's breaking somewhere inside the DPRINT1... odd.
Oh right, it's clear now : it's the "q" key I have to tap (when I'm asked to) to be able to make appear what looks missing AT THE BEGINNING of the back trace ? I did notice that the proicess started very quickly and that the beginning looked odd...
I'll do that then
![[ external image ]](https://s14.postimg.org/mq6pjfttt/before_back_trace_pic.jpg){kind=link}
![[ external image ]](https://s14.postimg.org/fa7fy38tt/after_back_trace_pic.jpg){kind=link}