AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
I uninstalled and reinstalled it, but I am not sure if it was the same Since a Windows 10 update it takes a very long time to load. Takes a while to learn how to use Wine and to get things working properly.I really like Winamp, and it works fine on my Windows 7 machine. Using Wine is almost like learning a new operating system. Go to the Wine web site and see what it says about a specific program and issues. What version of Windows you want Wine to mimic can affect how a program runs. Should download and install them as part of the initial config.Īlso, in Wine config->Drivers Select autodetect to get all the driver locations loaded in Wine.Ī lot of settup options in Wine config, so check them all. It will probably offer you a few more programs needed for Wine to run properly. When you get Wine installed and the Wine menu entries. Make sure you have the latest version of Wine.Īlso, look on the first post of the Wine topic for a added 'wine_extras-v2.1.pet' that puts Wine entries in the menu. If you have any Wine sfs packages loaded. Reboot to make sure the changes are saved. pet for 'winecfg' & the WINE 'dashboard'. Here's Winamp running in Xenialpup64 7.5, with the 'Pioneer 3.0' skin:. After install, you'll find it under Menu->System. pet below if you wish to avail yourself of it. OK both of these, because things won't function properly unless you do.Īfter the /root/.wine directory has been set up, the Menu entry then gives you access to the WINE 'dashboard':. NET framework), and Gecko (which enables HTML rendering within WINE). You'll usually be asked if you want to install MONO (the WINE Project's version of the. I install WINE, then I click on the Menu entry, and it performs its magic. I install that first, so it's sitting there ready, waiting. Personally, I have a 'MenuEntry' I've made up for this very purpose. Until that command has been run, you're wasting your time. This is your Windoze 'virtual environment', from where your programs/apps will work. What this does is to create and set-up the hidden '.wine' folder in /root. It will take a while, I can guarantee that.Īlong with WINE 1.7.51, the version of Winamp I use is this one:. Try 'em out find the one that works, the greatest part of the time, with the largest number of your particular Windows apps.then stick with it. There's scores of versions readily-available. I almost always use version2013's WINE 1.7.51 (quite an old version, it's true).but for my particular set of Windoze apps, it works perfectly.Īs the old saying goes 'If it ain't broke, don't 'fix' it.' I rather suspect that since Windows uses newer & newer dlls all the time (and M圜rudSoft have long-since dropped support for XP itself), that this is partly why I find that many of my apps don't run so well with 'new', 3-series WINE. I do know this much if you want to run XP-era apps, you're better off with older versions. By & large, it's steadily improving as the years go by, but it's a case, much of the time, of 'two steps forward, one step back'ards.' And that doesn't includes the Windows releases that each version purports to be compatible with. Oft-times, you'll find that an application which worked fine under one version will be broken in the next. I do know extra jiggery-pokery is involved.Ĭommon wisdom, according to many here, is to always use the very newest version available. There are now 64-bit WINE Puppy packages, but I've no idea how you use these. Winamp will then simply install from its. In my 64-bit Pups, I've first installed the 32-bit_compatibility_libs SFS package.followed by installing a 32-bit version of WINE. I'll state, here & now, that I have no experience of FatDog.
0 Comments
Read More
Leave a Reply. |