If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Incompatible programs
Brian Gregory wrote:
On 08/11/2014 14:29, Jeff Gaines wrote: On 08/11/2014 in message Bob Henson wrote: Hmm, it would appear I can't do that with the VM player - I have to fork out £160 quid for the paid version. Bob How about VirtualBox: https://www.virtualbox.org/ It's a Yorkshireman's favourite price :-) Yes I have Windows 10 TP running quite nicely in a VirtualBox 4.3.18 VM. The guest additions install and work too. The only odd thing is that I can't get the video display in the Virtual machine to be any size other than the standard 4:3 sizes 800*600, 1024*768, 1152*864 etc. In the Guest Device Manager, check to see if the Virtualbox driver is present for the video. In the Guest machine settings, make sure the frame buffer memory allocation is big enough. There are also options there to enable experimental Direct3D support and the like. The Win10 VESA fallback driver, would do 1024*768 here, so I recognize the symptoms. Win8 did the same thing. Previous OSes like WinXP, the fallback driver might do 800x600 or 640x480. Which is why I'd be checking Device Manager in your Guest, to see what driver is being used for video. The fallback driver gets used for my FX5200 card, since there is no driver from the manufacturer for it. In the Win10 Preview, a trip to Windows Update revealed an ATI/AMD driver for my HD6450, which fixed the resolution issue in a real, physical Win10 Preview installation. So you should be able to whip that install into shape, one way or another. There is bound to be a solution. Paul |
Ads |
#17
|
|||
|
|||
Incompatible programs
On 09/11/2014 22:27, Paul wrote:
Brian Gregory wrote: On 08/11/2014 14:29, Jeff Gaines wrote: On 08/11/2014 in message Bob Henson wrote: Hmm, it would appear I can't do that with the VM player - I have to fork out £160 quid for the paid version. Bob How about VirtualBox: https://www.virtualbox.org/ It's a Yorkshireman's favourite price :-) Yes I have Windows 10 TP running quite nicely in a VirtualBox 4.3.18 VM. The guest additions install and work too. The only odd thing is that I can't get the video display in the Virtual machine to be any size other than the standard 4:3 sizes 800*600, 1024*768, 1152*864 etc. In the Guest Device Manager, check to see if the Virtualbox driver is present for the video. In the Guest machine settings, make sure the frame buffer memory allocation is big enough. There are also options there to enable experimental Direct3D support and the like. The Win10 VESA fallback driver, would do 1024*768 here, so I recognize the symptoms. Win8 did the same thing. Previous OSes like WinXP, the fallback driver might do 800x600 or 640x480. Which is why I'd be checking Device Manager in your Guest, to see what driver is being used for video. The fallback driver gets used for my FX5200 card, since there is no driver from the manufacturer for it. In the Win10 Preview, a trip to Windows Update revealed an ATI/AMD driver for my HD6450, which fixed the resolution issue in a real, physical Win10 Preview installation. So you should be able to whip that install into shape, one way or another. There is bound to be a solution. Paul It's using "VirtualBox Graphics Adapter for Windows 8" I think that probably when they added support for Win10TP to the guest additions for VirtualBox 4.3.18 they didn't quite get everything working. -- Brian Gregory (in the UK). To email me please remove all the letter vee from my email address. |
#18
|
|||
|
|||
Incompatible programs
On 09/11/2014 10:16 PM, Paul wrote:
Bob Henson wrote: That works just fine - I would never have looked in My Documents for the directories, if you hadn't pointed out the working directory setting. The first thing I noticed from the three VMs I have is that the two Linux ones are about 8Gb and the Windows 10 one is 28Gb (with a few extra programs installed - but not many). Anyway, tomorrow when I have some (considerable, probably) time I'll .zip them up and store them on my backup drive. Thanks again for the help - that will make life considerably easier. There are data reclamation procedures you can do on things like .vhd files to make them smaller. If intending to compress such a file for long term storage, you might do something like that as the first step. Every time a virtual disk does a storage operation, there is an opportunity to create a non-zero sector in the process. The .vhd format, doesn't use physical space, for any sector that contains exactly 512 zeros. Once a sector goes "non-zero", then a real sector of storage is burned up by the container. To take advantage of that, you use any tool that creates a file of zeros. You can't use fsutil for this on NTFS, because it creates sparse files. You want a utility that physically writes every sector it says it will write. dd.exe if=/dev/zero of=C:\downloads\big00.dd bs=65536 When run in the guest, that writes zeros in any available data clusters, until all the space is gone. The very next command would be del C:\downloads\big00.dd That deletes the file, so the guest won't be complaining about all the space being gone. Now, all the sectors visited, contain zeros, and are candidates to be chucked out of the container. Now, shut down the VM. The VM hosting software, should have a tool for working on .vhd or similar images. One option, is to "re-write" a .vhd. In the process, if the tool finds a sector which contains 512 bytes of zeros, the newly created copy of the .vhd, will not have a physical sector stored on the host disk. So all of the zeroed out space is reclaimed, with respect to the size of the .vhd on the host file system. So for example, say the .vhd in the real world is 40GB, and inside the host the partitions total 28GB of used space. By doing the above procedure, when the .vhd is written out, it will be ~28GB. For OSes that have pagefiles and hiberfiles, you likely have further options for "cleaning". Only worthwhile for long term storage perhaps. You might be able to get Win10 down to about 14GB or so, with a little work. But if you're only going to open Win10 tomorrow, fiddling with the pagefile wouldn't be worth it. I have a partition that has nothing but VM images on it, and there is only about 50GB of free space left. And on occasion, I do a data reclamation on one of the bigger .vhd files, in order to keep some free space available on the partition. It's not the kind of thing to make a fetish out of it, but if a .vhd has gone for a couple of years without maintenance, it might benefit from a sprucing up, to make the wasted space smaller. Once a partition is cleaned that way, and the .vhd is smaller, you can then compress it for a further saving. You could do 7Z ultra for example. But that has a tangible cost - it might cost you a dollar of electricity, to compress a 1TB hard drive sized image that way. The compression runtime can be quite long. Paul Thanks. I've saved your message again, and I may well have a look those ideas. For the moment, I only need to save the one VM, so I'll probably just copy it across to my backup drive uncompressed. -- Bob Tetbury, Gloucestershire, UK No matter how much you push the envelope, it'll still be stationery |
#19
|
|||
|
|||
Incompatible programs
On 10/11/2014 01:57, Brian Gregory wrote:
On 09/11/2014 22:27, Paul wrote: Brian Gregory wrote: On 08/11/2014 14:29, Jeff Gaines wrote: On 08/11/2014 in message Bob Henson wrote: Hmm, it would appear I can't do that with the VM player - I have to fork out £160 quid for the paid version. Bob How about VirtualBox: https://www.virtualbox.org/ It's a Yorkshireman's favourite price :-) Yes I have Windows 10 TP running quite nicely in a VirtualBox 4.3.18 VM. The guest additions install and work too. The only odd thing is that I can't get the video display in the Virtual machine to be any size other than the standard 4:3 sizes 800*600, 1024*768, 1152*864 etc. In the Guest Device Manager, check to see if the Virtualbox driver is present for the video. In the Guest machine settings, make sure the frame buffer memory allocation is big enough. There are also options there to enable experimental Direct3D support and the like. The Win10 VESA fallback driver, would do 1024*768 here, so I recognize the symptoms. Win8 did the same thing. Previous OSes like WinXP, the fallback driver might do 800x600 or 640x480. Which is why I'd be checking Device Manager in your Guest, to see what driver is being used for video. The fallback driver gets used for my FX5200 card, since there is no driver from the manufacturer for it. In the Win10 Preview, a trip to Windows Update revealed an ATI/AMD driver for my HD6450, which fixed the resolution issue in a real, physical Win10 Preview installation. So you should be able to whip that install into shape, one way or another. There is bound to be a solution. Paul It's using "VirtualBox Graphics Adapter for Windows 8" I think that probably when they added support for Win10TP to the guest additions for VirtualBox 4.3.18 they didn't quite get everything working. I'm now on VirtualBox test build 4.3.19r96825 and everything is working. It could even be that it was all working in 4.3.18 but I did something wrong - I had to fiddle with some settings in 4.3.19r96825 before it came right. -- Brian Gregory (in the UK). To email me please remove all the letter vee from my email address. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|