Conversation
Notices
-
well, this is frustrating... I can no longer install a program with wine, q4wine is giving errors (suggests I need to install 'wine32' huh? no such thing); and Virtual box grumbles and also tells me there is a new version, I find out I need to UNinstall it before I can actually see the new version, and then installation fails with 'dependency problems' - none of which can be seen in dependencies in Synaptic (all dependencies are fulfilled); there's also a suggestion to run '/etc/init.d/vboxdrv setup' which gives no output at all (it's suposed to check for a new kernel and compile a new kernel module - which probably _should_ happen but apparently doesn't); log file is a sea of errors. #stuck
-
hope you figure your #wine and #virtualbox problems out soon
-
@erkan yeah... there are some Windows tools I still really need, at the very least to convert own-format graphical files into a format that can be read by others
-
-
"before I can actually see the new version": I remember a vbox version where chekcing updates didn't work because it made a connextion and couldn't handle the ssl certificate. https://www.virtualbox.org/query?status=!closed&keywords=~ssl
-
@erkan yeah, well, that hurdle is already taken because I did uninstall 4.2.x and now see 4.3.x (and 4.2.x is listed but no longer installable: just a name, no versions)
-
@mk Hmm I'm finding a hint that the old version needs to be *purged* (apparently as opposed to merely 'uninstalled'). #lunch first, I'm hungry!
-
@mk SUCCESS! Indeed, *purging* the old version of VirtualBox was the answer - but that took some doing because - having close Synaptic - it had disappeared from view. Some ddg-ing about purging brought the solution - and apart from a list of uninstalled programs that had 'virtualbox-4.2' there also was something called 'wine-bin'. Even before purging the old VirtualBox, I *reinstalled* wine-bin (it automatically took the latest, not the uninstalled version), and that included something called 'wine32' - precisely what q4wine had been grumbling I should install (but could not find)!
-
@mk I have by now purged the old VirtualBox, installed (without any more errors!) the new one, and have verified that it starts my (not purged!) VM. It needs further work now, but that's for l;ater. Let's see if Wine now behaves as well... :) #firster, #nowineedabeer! !beer #virtualization /cc @erkan
-
@mk So, apart from time for food and drink I've been struggling with this all day! I shoudl take a *real break and move away from my keyboard for a bit. #sudoku, I think :) #rest
-
@mk Final result: Wine completely purged - and that wasn't easy because it was a mess with different versions. I'll wait till it's all complely updated to the latest, and then see what the options are. One problem is that Synaptic only shows teh 64-bit version, while some tools require *both* 32-bit and 64-bit versions, or at least the 32-bit ones. If I can't find them through apt/Synaptic, I'll get them from pkgs.org. Meanwhile I've learned a bit about the scripted rules apt applies, so time not completely wasted.
-
@mk #tomorrow I'll install the new guest extensions in the Virtual machine I already have (Win Vista) and see if I can make a new one for Win7.
-
-
-
-
-
