lapino

[lapino]

No solution yet. I tried reinstalling lcdwriter and applying the settings you stated in the Moncaso review. It does seem to find that it’s on COM7, but when I click “Detect settings” it says access to com7 is denied (maybe this is what causing the errors after sleep?).

[lapino]

No solution yet. I tried reinstalling lcdwriter and applying the settings you stated in the Moncaso review. It does seem to find that it’s on COM7, but when I click “Detect settings” it says access to com7 is denied (maybe this is what causing the errors after sleep?).

[lapino]

I checked my bios (I have an ASROCK 880G/USB3 mainboard) but there seems to be S1/S3 settings there. The release notes for the newer FTDI drivers specifically state issues with sleep are fixed, but when I check my COM port, it seems to be using the new drivers already??

[lapino]

I checked my bios (I have an ASROCK 880G/USB3 mainboard) but there seems to be S1/S3 settings there. The release notes for the newer FTDI drivers specifically state issues with sleep are fixed, but when I check my COM port, it seems to be using the new drivers already??

[lapino]

Just did that (at least I think I have the latest one). I did find out that when I disable the ‘hybrid sleep mode’ in energy settings, it works (but then the htpc isn’t shut down completely). When I enable this (and thus getting the htpc to spin down fans etc), it gives me the error upon wake.

[lapino]

Just did that (at least I think I have the latest one). I did find out that when I disable the ‘hybrid sleep mode’ in energy settings, it works (but then the htpc isn’t shut down completely). When I enable this (and thus getting the htpc to spin down fans etc), it gives me the error upon wake.

[Author]

Posts