does not work, black screen.

[misterhsp]

see topic

...

[JaapJoris]

Hi there!

It works for me and many others. Have you followed the instructions? At which point do you see the black screen?

[misterhsp]

I only briefly see the Windows logo and black screen with blinking cursor in the upper left. And yes, I have followed the instructions

Am 10.10.23 um 20:42 schrieb Jaap Joris Vens:

Hi there!

It works for me and many others. Have you followed the instructions? At which point do you see the black screen?

— Reply to this email directly, view it on GitHub https://github.com/rtts/win311/issues/2#issuecomment-1756025669, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKGJLRMFDCE2LRXIBI7E243X6WJKTAVCNFSM6AAAAAA5UPP6WCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJWGAZDKNRWHE. You are receiving this because you authored the thread.Message ID: @.***>

[misterhsp]

How do you get 1280x1024 video with Qemu? Do you have a howto and where to get the driver for it? Maybe a howto for it?

Thanks....

[mmmmmmbeer]

I had the same issue following the instructions exactly. It appears to be hanging on network startup. I was able to launch windows successfully by mounting hda.img and changing the autoexec.bat to run win /n instead of just win

[JaapJoris]

That's a shame. It used to work including networking. Currently, I cannot get it to boot even with win /n. It just hangs showing this:

Since hda.img hasn't changed since it was first committed 3 years ago, this must have been caused by one of the recent changes to QEMU's ne2000.c, which means that this remark in the README may no longer be correct:

The installed driver is for the Realtek 8029 networking adapter, which is the one that is actually emulated with QEMU's ne2k_pci option (thank you Friedemann Baitinger for pointing me in the right direction in this 2004 forum post).

I mounted the hda.img mounted with ./mount, and looked at various *.ini and *.inf files beneath the c:\windows directory. It may be possible to deactivate the network only so you can still enjoy the games and other software. If anyone knows how, please chime in.

The last time I had to solve this problem I was 10.

[mattman86]

I got it to work with the following command:

qemu-system-i386 -nic user,ipv6=off,model=ne2k_pci -drive format=raw,file=hda.img -vga cirrus -device sb16 -display gtk

Only issue is that it sometimes freezes and I have to close the QEMU window and boot back up.

[misterhsp]

That doesn't work for me either. I still see the Windows logo and then black screen.

Am 26.04.24 um 21:29 schrieb Matthew Despain:

I got it to work with the following command:

|qemu-system-i386 -nic user,ipv6=off,model=ne2k_pci -drive format=raw,file=hda.img -vga cirrus -device sb16 -display gtk|

Only issue is that it sometimes freezes and I have to close the QEMU window and boot back up.

— Reply to this email directly, view it on GitHub https://github.com/rtts/win311/issues/2#issuecomment-2080003316, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKGJLRMQY7DIWLB2GSANNFTY7KTIXAVCNFSM6AAAAAA5UPP6WCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGAYDGMZRGY. You are receiving this because you authored the thread.Message ID: @.***>

[JaapJoris]

~IT WORKS AGAIN!~

Well, at least for me, using QEMU emulator version 8.2.3 (Debian 1:8.2.3+ds-2).

Edit: this may have been a fluke, see this message further down this thread:

The problem does not appear to be consistent though, for example if I run many instances of it at once, on say, v9.0.0, usually at least one of them will actually boot correctly.

[misterhsp]

Even if you don't like it, it's still black screen here. Even with the version you mentioned.

Am 09.05.24 um 22:23 schrieb Jaap Joris Vens:

IT WORKS AGAIN!

Well, at least for me, using |QEMU emulator version 8.2.3 (Debian 1:8.2.3+ds-2)|.

Beware that if you don't use the |-snapshot| argument, you are at risk of breaking the |hda.img|. When that inevitably happens, rest assured you can always download a new one from https://rtts.eu/download/win311/hda.img

— Reply to this email directly, view it on GitHub https://github.com/rtts/win311/issues/2#issuecomment-2103361353, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKGJLRP2EOBLRNZ2GHQQBY3ZBPLNFAVCNFSM6AAAAAA5UPP6WCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTGM3DCMZVGM. You are receiving this because you authored the thread.Message ID: @.***>

[popey]

I just stumbled on this repo via a link from another forum. I also had a black screen issue.

However, Good News, Everyone! It's easily fixed. Here's a screenshot of it on my ThinkPad running Ubuntu.

I agree with the previous comments about updates to QEMU being the problem.

So, I went back and found the version of QEMU that would have been contemporary when @JaapJoris uploaded the image. QEMU 5.0.2 was released in December before the upload, so I suspect that may have been the release they used.

I grabbed the source from https://download.qemu.org/ - precisely this tarball.

I compiled it on my Ubuntu 24.04 laptop, mostly ./configure and make -j8. It needed apt install ninja and probably wouldn't hurt to apt-get build-dep qemu to get build dependencies required by the Ubuntu package.

I then copied the qemu-system-i386 binary and the various ROMS from the pc-bios/ folder too into the folder where the start script and hda.img are. That includes bios-256k.bin, efi-e1000.rom, efi-ne2k_pci.rom, vgabios-cirrus.bin, vgabios-stdvga.bin, kvmvapic.bin. I then tweaked the start script to use the local qemu-system-i386.

All working fine.

[JaapJoris]

Oh god, I can see where this is going: in a few decades from now when someone recovers this repository from the arctic vault, someone will have to set up Ubuntu 24.04 in an emulator as the only way to run Windows 3.11 on a post-apocalyptic machine.

In order to help them with the visibility of this, I'll reopen this issue.

[otonoton]

@popey Why not bisect the qemu code to find the exact commit that caused the issue so it can be reported and fixed?

[popey]

Because I wanted a quick and easy fix.

Feel free to do the lengthy work of bisecting until you find the right patch.

[otonoton]

@popey I bisected it, looks like it has been broken since 7.2.0:

2255da493a92e0f6441c773fa3bfdfb34273e85f is the first bad commit
commit 2255da493a92e0f6441c773fa3bfdfb34273e85f
Author: Richard Henderson <richard.henderson@linaro.org>
Date:   Sat Oct 1 07:09:27 2022 -0700

    target/i386: Use gen_jmp_rel for loop, repz, jecxz insns

    With gen_jmp_rel, we may chain to the next tb instead of merely
    writing to eip and exiting.  For repz, subtract cur_insn_len to
    restart the current insn.

    Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
    Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
    Message-Id: <20221001140935.465607-19-richard.henderson@linaro.org>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

 target/i386/tcg/translate.c | 36 +++++++++++++++---------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

[otonoton]

The problem does not appear to be consistent though, for example if I run many instances of it at once, on say, v9.0.0, usually at least one of them will actually boot correctly. This will run 8 instances at once:

parallel -N0 qemu-system-x86_64 -hda hda.img -nic user,ipv6=off,model=ne2k_pci -device sb16 -vga cirrus -snapshot -no-shutdown -display gtk,zoom-to-fit=on ::: {1..8}

[Trash-o-ljub]

oke... so can somebody help me to run it on mac 15 with latest QEMU? or any way of click-click boom setup? why is image corupted aAAAA! there is a problem in ./mount with "-o loop" option not supported and in ./start with -display gtk (that I figgured out it should say "-display cocoa" I think)