Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles
On Friday, August 11, 2017 at 1:39:52 PM UTC-7, PR wrote: > Hello Daniel, > > > > when working with Qubes, I write all information into my own Wiki. > > Here my notes regarding the installation of a Window 7 HVM: > > > > Windows HVM > > Skip to end of metadata > > > > See also: https://www.qubes-os.org/doc/windows-appvms/ > > > > > Update Windows Tools > > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > qubes-windows-tools > > > > > Mount External HDD containing the windows installer ISO to the > VM untrusted > > qvm-usb -a untrusted sys-usb:4-3 > > > > > Create new windows VM > > qvm-create win7 --hvm --label green > > > > > Start new windows VM with attached installer-ISO > > qvm-start globits > --cdrom=untrusted:/run/media/user/WDEXT2TB/win7pro-32-de.iso > > (will start the VM and run the installer ISO) > > > > > First restart after ~4 min > > restart manually qvm-start globits > > > > > Further installation, restart manually > > qvm-start globits > > > > > Further installation, restart manually > > qvm-start globits > > > > > Start into Desktop / Updates -> decide later > > > > > Allow unsigned drivers by opening a CMD as administrator > > bcedit /set testsigning on > > > > > Install Windows Tools > > qvm-start globits --install-windows-tools > > > > > Change qrexec timeout because User Folder will be moved > > qvm-prefs -s qrexec_timeout 300 > > > > > Enable Debug Mode via Qubes Manager GUI > > > > > Enable auto-Login by starting netplwiz within Windows vm > > > > > Enable Seamless Mode / Disable Debug Mode via Qubes Manager > GUI > > > > Attention: > > i had big problems getting seamless mode to work, and found out the > reason after lots of troubleshooting. > > It seems that seamless mode will not work with all display > resolutions. > > I have 3 K-display with a native resolution of 2.880 x 1.620 Pixels. > > > With this resolution seamless mode didn't work, I had to change the > resolution to a standard resolution. > > > > You might also look here: > > https://groups.google.com/forum/#!msg/qubes-users/Ia73yb4lCGA/s8Qp9dl4CQAJ > > > > https://github.com/QubesOS/qubes-issues/issues/1896 > > > > Which resolution are you using in Qubes? > > > > - PhR > > > > > > > > > On 08/11/17 22:02, Daniel Nelson wrote: > > > > On Friday, August 11, 2017 at 8:29:09 AM UTC-7, yura...@gmail.com wrote: > > > On Friday, August 11, 2017 at 12:04:44 AM UTC, Daniel Nelson wrote: > > > Did you ever make additional progress on your problems with QWT? I > encountered all the same issues you did, and the one I've not been able to > solve is always having to run my Win7 apps in debug mode, thus losing the > possibility of lovely seamless integration. > > I tried what you suggested about backing out the latest QWT and installing > the previous version. I tried it first with simply uninstalling from my VM, > with quirky results, so I went ahead and created a fresh VM. This > particular behavior continues, though, also with the GUI agent outdated > protocol error on exit, and usually with two Win7 related QubesDB files that > need to be manually deleted prior to relaunching as well. > > > Did you try the opposite approach and use the packages from the > testing repositories? > > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > qubes-windows-tools > > I'm unaware if the fix is still in testing, however the MegaTraveller guy > verified (28 December, 2016) that this worked for him, in this thread > https://github.com/QubesOS/qubes-issues/issues/2488 > > Also, as annoying and time consuming it may be, you might want to make a > fresh HVM install again. As far as I've understood, it's not recommended
Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles
On Friday, August 11, 2017 at 8:29:09 AM UTC-7, yura...@gmail.com wrote: > On Friday, August 11, 2017 at 12:04:44 AM UTC, Daniel Nelson wrote: > > Did you ever make additional progress on your problems with QWT? I > > encountered all the same issues you did, and the one I've not been able to > > solve is always having to run my Win7 apps in debug mode, thus losing the > > possibility of lovely seamless integration. > > > > I tried what you suggested about backing out the latest QWT and installing > > the previous version. I tried it first with simply uninstalling from my > > VM, with quirky results, so I went ahead and created a fresh VM. This > > particular behavior continues, though, also with the GUI agent outdated > > protocol error on exit, and usually with two Win7 related QubesDB files > > that need to be manually deleted prior to relaunching as well. > > Did you try the opposite approach and use the packages from the testing > repositories? > > sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > qubes-windows-tools > > I'm unaware if the fix is still in testing, however the MegaTraveller guy > verified (28 December, 2016) that this worked for him, in this thread > https://github.com/QubesOS/qubes-issues/issues/2488 > > Also, as annoying and time consuming it may be, you might want to make a > fresh HVM install again. As far as I've understood, it's not recommended to > re-install QWT. > I would however suggest to make a fresh backup of your Win7 from the moment > it's just freshly installed, so you don't have to do more work than needed in > the future. Thanks very much for the additional link. I'll do more reading. As to your questions... I was unable to fetch QWT from the live repo. I've been using only what I can get from the test repo. I tried both ways of doing things already... meaning that I tried uninstalling the tools from the Win7 VM, removing them from Qubes, fetching the previous version, then installing them into the VM. Since that didn't work I then did it the other way (deleting the VM and starting from scratch, but still with the previous version of QWT). The first way gave a pretty unstable Win7 VM. The second way worked fine, but the exit errors and lack of seamless functionality was the same as with the latest version of QWT. I'll dig more into the link you provided and see if I can find some joy. Thanks again! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c6c5cffc-bfc2-4169-a4a5-b7c3a9dcc856%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles
Did you ever make additional progress on your problems with QWT? I encountered all the same issues you did, and the one I've not been able to solve is always having to run my Win7 apps in debug mode, thus losing the possibility of lovely seamless integration. I tried what you suggested about backing out the latest QWT and installing the previous version. I tried it first with simply uninstalling from my VM, with quirky results, so I went ahead and created a fresh VM. This particular behavior continues, though, also with the GUI agent outdated protocol error on exit, and usually with two Win7 related QubesDB files that need to be manually deleted prior to relaunching as well. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4aaec58b-e82f-4d72-b8c3-91af349c8279%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
