filecopy works even if drivers fail silently, so no worries. also you may make an iso image and attach it.
How did you create Win7 qube with 4.1x at all?
What do you mean by “drivers fail silently”? It fails to boot the whole OS.
also you may make an iso image and attach it.
How do you attach it?
from qubes settings or qvm-start --cdrom
I don’t know what you are asking.
I am running Qubes 4.3.1.
How exactly do you initiate installing QWT?
Hm. I thought that was only for booting from CD.
I will try. Thanks.
qvm-start WIN7 --install-windows-tools
And what version do you have installed in dom0?
That will probably be 4.2.2 which cannot use its PV divers.
Yep. That’s why it doesn’t work. So either downgrade to 4.1.69, if that is possible at all, or edit win 7 iso, put there qwt 4.1.69.msi, rebuild iso and boot installation of win 7, then after installation mount it again to copy paste it to win 7 and start manual installation from within Standalone VM (or from the mounted iso inside win 7 installed).
As I already explained, I use Qubes 4.3.1 and qubes-windows-tools-4.1.69-1.fc37.noarch.rpm.
I also found that QWT or no QWT - the Q: drive disappears after reboot.
You never told full facts. For example, how you got 4.1.69, did you downgrade, or just downloaded it to dom0, what are qvm-features and prefs of the qube, etc. You won’t be helped that way. I have a fully functional win 7 standalone under r4.3.1 and it works flawlessly with 4.1.67. We spent 53 posts so far in order to help you, but honestly, it looks like you want to prove there is no solution to this more than vice versa.
I don’t understand what you mean. I answered every question. If I have missed any, please let me know.
Answering your latest in order:
For example, how you got 4.1.69, did you downgrade, or just downloaded it to dom0,
I downloaded it and installed it in dom0 as described in the docs for Windows 7.
what are qvm-features and prefs of the qube
As per docs:
qrexec_timeout 7200
timezone localtime
The qvm-features for audio-model didn’t work, so I am not using that. I don’t need audio anyway.
etc.
Please let me know if you miss any other info.
I have a fully functional win 7 standalone under r4.3.1 and it works flawlessly with 4.1.67.
The docs and QSB-091 talk about 4.1.69, so I have no idea about your version.
It’'s about the same.
What are you talking about? (This shows as a reply the OP here, not to a particular post)
FWIW, after all the unsuccessful attempts, I downloaded and installed Windows 11 (doh…). In a copy of the template, I was able to install QWT. It works as long as the experimental GUI drivers are not installed. However (!):
While working with copies of the VM to test all this, everything seemed to work fine. After that, I deleted the copies and installed QWT in the original Windows 11 qube.
Result:
“The referenced account is currently locked out and may not be logged on.”
I really don’t understand. How come the exact same steps in a clone of the qube worked and now they don’t?
Is there a fix or must I reinstall from scratch?
P.S. After rebooting the qube again, it works.
The miracles of software…
Good for you. Now, let’s hope the ancient software still works under Win 11.
Thanks.
So far, it seems most of the UI is not clickable even in compatibility mode.
Can anyone confirm if TemplateVM with a working Q: drive for AppVMs is even possible for Windows 7?