subject:"Re\: \[qubes\-users\] Win 7, Qubes 3.2, qubes\-windows\-tools 3.2.2\-3 struggles"

Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles

2017-08-21 Thread Drew White

On Saturday, 19 August 2017 03:14:40 UTC+10, Daniel Nelson  wrote:
> That seems to be a great question!  I have no idea what the answer is.  :-)  
> I can only say that I experienced the same problem symptoms that several 
> people before me did - that Windows setup hung at the initial boot screen 
> with glowing logo.  Following the same steps that helped many others also 
> helped me (changing to Cirrus driver).  All the details to the how are 
> summarised nicely here:  https://github.com/QubesOS/qubes-issues/issues/2488. 
>  I don't recall any mention of the why, though.

(I have never personally had this issue on ANY of the machines that I have used 
that has required this as a fix.)

I have had it lock once before because of other issues, which i just had to 
restart the pc to unlock the loops to get it working again.

> I guess I can also say that my system is a standard Intel Skylake Core M7 
> utilising the on-processor Intel HD graphics, and that my BIOS is a 
> combination of Coreboot and Tianocore, purely UEFI.  Just some fundamental 
> driver incompatibility maybe.

Perhaps.

> 
> 
> Incidentally, in case it might help anybody that comes after me and reads 
> this thread...
> 
> 
> I upgraded from the previous build of QWT to the latest (3.2.2-3) since the 
> previous version didn't work particularly better for me.
> Since then I was able to run Windows apps at least twice in seamless mode, no 
> debug!  It's pretty random, though.  It fails to display a window at all most 
> times, and the VM has to be killed.  I will try to find time to look deeper, 
> maybe increase the loglevel of some of the components and see more of what's 
> happening when it fails vs. when it succeeds.  Not sure on when I can find 
> the time for that, but I'll try to remember to report back if I find anything 
> that allows me to get it working consistently all the time.  For now I've 
> accepted running it always in debug mode for the stability.
> 

I am currently running the latest version. And I am having no issues on my 
laptop at this resolution.
1366x768
I also have my PC running at 1080p

My Dual Monitor Desktop is one monitor at 1920x1080 and the other at 1600x900
And that works fine.

But anything larger than that I have to run the system BEFORE i activate those 
screens and have the UI be notified of the size change to then do the resize 
after it's all working correctly and active.


-- 
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/b2c59029-02ee-47e8-8571-dcd162b51f00%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

2017-08-18 Thread Adrian McLeod

That seems to be a great question!  I have no idea what the answer is.  :-)

I can only say that I experienced the same problem symptoms that several
people before me did - that Windows setup hung at the initial boot screen
with glowing logo.  Following the same steps that helped many others also
helped me (changing to Cirrus driver).  All the details to the how are
summarised nicely here:  https://github.com/QubesOS/qubes-issues/issues/2488.
I don't recall any mention of the why, though.
I guess I can also say that my system is a standard Intel Skylake Core M7
utilising the on-processor Intel HD graphics, and that my BIOS is a
combination of Coreboot and Tianocore, purely UEFI.  Just some fundamental
driver incompatibility maybe.

Incidentally, in case it might help anybody that comes after me and reads
this thread...

I upgraded from the previous build of QWT to the latest (3.2.2-3) since the
previous version didn't work particularly better for me.
Since then I was able to run Windows apps at least twice in seamless mode,
no debug!  It's pretty random, though.  It fails to display a window at all
most times, and the VM has to be killed.  I will try to find time to look
deeper, maybe increase the loglevel of some of the components and see more
of what's happening when it fails vs. when it succeeds.  Not sure on when I
can find the time for that, but I'll try to remember to report back if I
find anything that allows me to get it working consistently all the time.
For now I've accepted running it always in debug mode for the stability.

On Thu, Aug 17, 2017 at 6:44 PM, Drew White  wrote:

> On Tuesday, 15 August 2017 03:19:03 UTC+10, Daniel Nelson  wrote:
> > Thanks for all the additional notes.  Everything you did perfectly
> matched what I've done  except that I also had to copy the win7.conf and
> edit it to change the video from "xen" to "cirrus," which is also pretty
> well documented in various places.  I had to do this both during Windows
> install, and then again during QWT install, but it worked as advertised.
> > The one thing I've not done too much fiddling with is the resolution.
> I've tried 1024x768 without joy.  I will continue to investigate further
> with different resolutions, and I will try also to more permanently change
> the video driver in use.
> >
> > Thanks again!
>
> Why do you all have to change from Xen to Cirrus in the config?
>
> I use XEN as my video. And I have no issue with many graphical things now.
>
> Only time I have issues is when I try to start the Windows Guest when I'm
> running 5 monitors. As long as I start it with only 1, then proceed to add
> the rest, it's fine. But I've said all this before so I swill not repeat it
> all over again.
>
> But that's the only real issue I have with the video side of it.
>
> So I am just curious as to why so many people I see are having to change
> to Cirrus from XEN?
>

-- 
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/CAB-xJPfnDNZsCNdBnViyiYjr7Qo2jH%3DrfPf%2B4B1tw3RqdKJ1LQ%40mail.gmail.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

2017-08-17 Thread Drew White

On Tuesday, 15 August 2017 03:19:03 UTC+10, Daniel Nelson  wrote:
> Thanks for all the additional notes.  Everything you did perfectly matched 
> what I've done  except that I also had to copy the win7.conf and edit it to 
> change the video from "xen" to "cirrus," which is also pretty well documented 
> in various places.  I had to do this both during Windows install, and then 
> again during QWT install, but it worked as advertised.
> The one thing I've not done too much fiddling with is the resolution.  I've 
> tried 1024x768 without joy.  I will continue to investigate further with 
> different resolutions, and I will try also to more permanently change the 
> video driver in use.
> 
> Thanks again!

Why do you all have to change from Xen to Cirrus in the config?

I use XEN as my video. And I have no issue with many graphical things now.

Only time I have issues is when I try to start the Windows Guest when I'm 
running 5 monitors. As long as I start it with only 1, then proceed to add the 
rest, it's fine. But I've said all this before so I swill not repeat it all 
over again.

But that's the only real issue I have with the video side of it.

So I am just curious as to why so many people I see are having to change to 
Cirrus from XEN?

-- 
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/01aba21a-0638-4583-87d4-e215509c2be8%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

2017-08-14 Thread Daniel Nelson

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 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 install

Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles

2017-08-11 Thread 'PhR' via qubes-users

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

* 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 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/03a0d3cd-01dc-f4fc-7d39-9064966bba3f%40googlemail.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

2017-08-11 Thread Daniel Nelson

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

2017-08-11 Thread yuraeitha

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.

-- 
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/6ca9f91e-4416-4731-bd64-55fb4d4068fe%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

2017-08-10 Thread Daniel Nelson

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.

Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles

2017-03-12 Thread Drew White

On Saturday, 11 March 2017 03:47:03 UTC+11, Ed Welch  wrote:
> On 03/10/2017 01:28 AM, Drew White wrote:
> > Problem is, they don't care.
> I'm new to this OS and new to this community, however, after searching 
> many many threads for info, looking at git/documentation/etc.  I really 
> have not gotten this impression at all, I regularly see developers 
> responding to threads and offering assistance.

Perhaps I should have provided more information in that one statement than 
providing the information in the whole post.

It's the whole post that provides the full details, not just one line.

Things change, things get passed from person to person and not everything is 
passed on properly. So things go wrong. They do their best, and there are bugs. 
Thing is, they aren't really focused on the Windows side for the tools, because 
the bugs that were there in version 2, if they were fixed, then the bugs they 
are trying to fix now would not be there due to the root cause being fixed. And 
that gives the impression that they don't care that much about the GFX side, 
because everything else is working, and there are just some idiosyncrasies of 
it. I don't mean that they don't actually care, it's more of a turn of phrase 
rather than a literal meaning.


> >
> > There are bugs in the tools that I pointed out in version 2 of the tools, 
> > and they still aren't fixed.
> >
> > The worse the issues got, the more I pressed it, and the more issues they 
> > put in instead of fixing.
> >
> > Then they fixed one issue, and then started putting more in.
> >
> > 3.2.1.3 is alright and works, as I posted about months ago after I upgraded 
> > to 3.2.2.3 and it broke Windows and caused lag in the Qubes Video Driver 
> > along with a major flicker.
> >
> > The only way to resolve that was to remove QWT and then perform a complete 
> > reinstall of it, without the video driver.
> > But to do that I had to start in safe mode, and enable the standard display 
> > adapter and disable the Qubes Video.
> >
> > I've been complaining for so long about things it's not funny, and they 
> > have not resolved the issues. (yet) That was stared in Qubes 2.
> >
> > Now at Qubes 4, I don't expect there to be any advancement in the Windows 
> > integration for the GPU side of things.
> >
> > But I stick to Qubes for security, that's one thing that they did get 
> > right, the whole reason behind it.
> >
> > So all in all, since QWT changed hands a couple of times, things went wrong.
> > So in essence, I just hope for the future because having multiple people 
> > work on the QWT system and it going wrong mainly after it changed hands, 
> > was expected.
> >
> > So, in a few years, the bugs in QWT 2* GFX side might be fixed.
> > Maybe they might do a complete re-write and get it all resolved in a month 
> > or 2.
> >
> 
> I would say my experiences thus far have given me the impression windows 
> support is not a primary focus of this project.  Windows tools/support 
> seems to be mainly user contributed, and while mostly functional, Qubes 
> in no way offers the kind of windows experience running on bare metal 
> would get you.
> 

Well, as soon ass they started work on version 4, version 3 went to the very 
back burner. The developers told me that version 3 would be not worked on very 
much, if at all, by the developers after version 4 comes out.


> This is perfectly ok with me, and in my personal opinion I think if 
> someone is looking for a windows machine with full hardware acceleration 
> (to support something like game playing), Qubes (or almost any 
> virtualization technology) is not going to be the answer.
> 
> If I were to offer any criticism to the qubes project, strictly 
> regarding Windows support, it would be that their documentation should 
> set expectations of what Windows support is available a little more 
> clearly.  After looking at the Qubes homepage a few weeks ago before 
> heading down the road of installing it myself, I was mostly expecting 
> windows support to be on par with linux ( I was never expecting graphics 
> acceleration or much direct hardware, as it is made clear linux appvm's 
> do not support hardware acceleration). I was however expecting things 
> like usb passthrough to work, and I was troubled by problems with the 
> most recent version of QWT which the docs I don't think quite explained 
> (so I decided to help by submitting my experience to the news group 
> archive to hopefully help others)
> 
> 
> On a personal note, after reading a handful of your emails last night, I 
> found the tone of all your emails leaving a rather poor taste in my 
> mouth.  There was an arrogance and sense of entitlement that I think 
> totally detract from any useful information you may have been providing.
> 
> It sounds like you are doing good work with slackware and with good 
> purpose, but then I read comments like "I know more about qubes than the 
> developers do by now." and "I've been complaining for so

Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles

2017-03-10 Thread Ed Welch

On 03/10/2017 01:28 AM, Drew White wrote:

Problem is, they don't care.
I'm new to this OS and new to this community, however, after searching
many many threads for info, looking at git/documentation/etc. I really
have not gotten this impression at all, I regularly see developers
responding to threads and offering assistance.

There are bugs in the tools that I pointed out in version 2 of the tools, and
they still aren't fixed.

The worse the issues got, the more I pressed it, and the more issues they put
in instead of fixing.

Then they fixed one issue, and then started putting more in.

3.2.1.3 is alright and works, as I posted about months ago after I upgraded to
3.2.2.3 and it broke Windows and caused lag in the Qubes Video Driver along
with a major flicker.

The only way to resolve that was to remove QWT and then perform a complete
reinstall of it, without the video driver.
But to do that I had to start in safe mode, and enable the standard display
adapter and disable the Qubes Video.

I've been complaining for so long about things it's not funny, and they have
not resolved the issues. (yet) That was stared in Qubes 2.

Now at Qubes 4, I don't expect there to be any advancement in the Windows
integration for the GPU side of things.

But I stick to Qubes for security, that's one thing that they did get right,
the whole reason behind it.

So all in all, since QWT changed hands a couple of times, things went wrong.
So in essence, I just hope for the future because having multiple people work
on the QWT system and it going wrong mainly after it changed hands, was
expected.

So, in a few years, the bugs in QWT 2* GFX side might be fixed.
Maybe they might do a complete re-write and get it all resolved in a month or 2.

I would say my experiences thus far have given me the impression windows
support is not a primary focus of this project. Windows tools/support
seems to be mainly user contributed, and while mostly functional, Qubes
in no way offers the kind of windows experience running on bare metal
would get you.

This is perfectly ok with me, and in my personal opinion I think if
someone is looking for a windows machine with full hardware acceleration
(to support something like game playing), Qubes (or almost any
virtualization technology) is not going to be the answer.

If I were to offer any criticism to the qubes project, strictly
regarding Windows support, it would be that their documentation should
set expectations of what Windows support is available a little more
clearly. After looking at the Qubes homepage a few weeks ago before
heading down the road of installing it myself, I was mostly expecting
windows support to be on par with linux ( I was never expecting graphics
acceleration or much direct hardware, as it is made clear linux appvm's
do not support hardware acceleration). I was however expecting things
like usb passthrough to work, and I was troubled by problems with the
most recent version of QWT which the docs I don't think quite explained
(so I decided to help by submitting my experience to the news group
archive to hopefully help others)

On a personal note, after reading a handful of your emails last night, I
found the tone of all your emails leaving a rather poor taste in my
mouth. There was an arrogance and sense of entitlement that I think
totally detract from any useful information you may have been providing.

It sounds like you are doing good work with slackware and with good
purpose, but then I read comments like "I know more about qubes than the
developers do by now." and "I've been complaining for so long about
things it's not funny, and they have not resolved the issues. (yet)" and
I'm not sure if you realize just how off putting that is to someone who
is working very hard on an open source project.

The qubes developers do not owe us anything, rather quite the opposite,
we owe them immensely for all their hard work creating a fantastic
operating system!

--
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/6e5fe963-e0cf-2bb0-880c-94957e3c2de4%40edjusted.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

2017-03-09 Thread Drew White

Problem is, they don't care.