bootcd logfiles

[Bernd Blaauw]

Is there any documentation available for where ReactOS stores its 
logfiles? For a phase 2/3 installation to harddisk, obviously it gets 
stores on drive C: somewhere. For phase 1, screen and debugport 
(com/rs232) seem to be the only options. Same goes for the BootCD and 
LiveCD.

As I'm experiencing massive issues with getting ReactOS to boot on 
USB-enabled real-hardware systems, I'd like to boot from the CD and have 
ReactOS automatically write logfile to whichever first FAT filesystem it 
can find. Irrelevant if it's USB stick or ATA hdd-partition. Is this 
possible or even already done?

If above is not possible, which exact configuration settings would I 
need for Bochs or QEMU (so I get debug log file) to add:
* USB optical device (ISO file on host)
* USB harddisk (hdd-imagefile on host)
* USB mouse
* USB keyboard

Lacking a 2nd system and photocamera device, all that remains for 
obtaining logfiles is using an emulator, which usually configure their 
hdd/cd as ATAPI devices and input as PS/2 devices

I'm hoping an emulator will show same issues as on real hardware, and 
that the logfiles can add to bugreports already present.

Bernd

PS: tested 58013 and searched 
http://jira.reactos.org/secure/IssueNavigator.jspa for USB
PPS: Haiku happily boots up on this machine from my isostick device.

[Bernd Blaauw]

Op 26-12-2012 20:07, Bernd Blaauw schreef:
>   Is there any documentation available for where ReactOS
> stores its
>  logfiles? For a phase 2/3 installation to harddisk, obviously it gets
>  stores on drive C: somewhere. For phase 1, screen and debugport
>  (com/rs232) seem to be the only options. Same goes for the BootCD and
>  LiveCD. 
Nevermind, got ReactOS LiveCD working on real HW by the following:
1) remove all USB devices (keyb, mouse, drive storage, optical storage)
2) disable legacy availability of USB devices in BIOS.

Keyboard is on PS/2, mouse can be attached and works once desktop is 
visible.

Bochs doc: http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html
(section 4.2.30..32) shows the USB config part.

QEMU doc: http://www.kraxel.org/cgit/qemu/tree/docs/usb2.txt

I'll try to make myself usefull by experimenting with ROS in above 
emulators with USB on, see if I can get logs exposing same issues as 
real HW.

Bernd

[Minas Abrahamyan]

You could try to use my dmesg command for KDBG in DEBUG mode of ROS
LiveCD/BootCD:
It allows to read,browse the log while nothing works and nothing is
available, except the kernel.
It works only in DEBUG build of ROS

HTH,
-M.A.

On Thu, Dec 27, 2012 at 6:31 PM, Bernd Blaauw <bblaauw(a)home.nl> wrote:
>   Op 26-12-2012 20:07, Bernd Blaauw schreef:
>
> >   Is there any documentation available for where
> > ReactOS stores its
> >  logfiles? For a phase 2/3 installation to harddisk, obviously it gets
> >  stores on drive C: somewhere. For phase 1, screen and debugport
> >  (com/rs232) seem to be the only options. Same goes for the BootCD and
> >  LiveCD. 
>
>  Nevermind, got ReactOS LiveCD working on real HW by the following:
>  1) remove all USB devices (keyb, mouse, drive storage, optical storage)
>  2) disable legacy availability of USB devices in BIOS.
>
>  Keyboard is on PS/2, mouse can be attached and works once desktop is
>  visible.
>
>  Bochs doc: http://bochs.sourceforge.net/doc/docbook/user/bochsrc.html
>  (section 4.2.30..32) shows the USB config part.
>
>  QEMU doc: http://www.kraxel.org/cgit/qemu/tree/docs/usb2.txt
>
>  I'll try to make myself usefull by experimenting with ROS in above emulators
>  with USB on, see if I can get logs exposing same issues as real HW.
>
>  Bernd
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev