Thanks Thomas,

Yes and No...

I added Options=/DEBUG /DEBUGPORT=COM2 /BAUDRATE=115200 /SOS / KDSERIAL
which ended up on the BootCD all right, but it seems KD is never brought in, or doesn't
use the settings from freeldr.ini on the BootCD, so no trace :/
(Ok, /SOS was perhaps a bit over the top, but anyway.)

Do you know where the source is for what becomes 'freeldr.ini' on the HD
after installation?  If I can modify that, I can at least get a trace on the later
phases of installation, after ROS boots from HD.

Then I might get a hint on why the Wine Gecko installer is broken.
(It waits forever for whatever it might be.. Lucky it can be canceled.)
Speaking of which, shouldn't the Wine Gecko installer be included
in the RosApps list so one can install it later?  ATM it isn't.

Best Regards
L.

You should be able to simply add an
Options=...
line to the [Setup] section in boot/bootdata/bootcd.ini to modify
the setup's freeldr options. That file becomes freeldr.ini in the root
dir of the BootCD.


On 2016-09-27 12:21, Love Nystrom wrote:

> Good afternoon gentlemen..
> 
> Can anyone tell me at what point during ROS installation KD becomes 
> operative?
> And if there is a way to change the default KD COM port from COM1 to COM2
> in order to trace KD output during installation?
> 
> (I run my ROS tests on VMware with a com0com connection from ReactOS COM2
> to my host machine, which works fine after install is complete and I can 
> edit freeldr.ini,
> but I'd like to be able to collect KD output during installation as well.)
> 
> (COM1 is not an option, since it's a physical port on both host and guest.)
> 
> Do I have to patch KD itself ?
> 
> Best Regards
> L.

-- 
There is one thing stronger than all the armies in the world,
and that's an idea whose time has come. [Victor Hugo]