similar to: MEPIS - WIne won't load Photoshop

I have tried a few rtimes now to install Abobe PS7 (not a crack) on the latest Linux Mint and now on Ubuntu 8.10 64bit. I am having the same problem in both. Is it because my new comp is a 64bit? An error occurred while loading the archive. [/media/cdrom0/Autoplay.exe] End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part

I am a rank newb at this and I appologize, I would have dumped MS long ago but I am not any kind of a coder, so having to write scripts and such is out for me. I really want to dump everything microsoft.....but I have to be able to run Adobe Photoshop 7 and CS4......why do I keep PS7...because I can't get a lot of the plug-ins I use for any thing above 7 and a lot of the ones I can I have to

Hi I got wine from Sourceforge and extracted it to a folder. In that folder I open a terminal and want to check dependencies . I get this : fuz at Fuzzy:~/linux saved/wine-0.9.58$ ./configure checking build system type... i686-pc-linux-gnulibc1 checking host system type... i686-pc-linux-gnulibc1 checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default

I have installed wine on my mepis 8.0 desktop and laptop. Wine runs Netscaper Navigator on the desktop but not on the laptop. Why??? (newbie asking). I'm on the desktop now asking the question---

I''ve just setup mepis. It comes with 1.8.4. I though it would be easy to install Rails on it. So, I downloaded the ruby gems. But when I try to install it using ruby setup.rb. It cannot find Rdoc. I''ve tried apt-get install rdoc. This gives an ''rdoc not found in repository'' I''m now to Debian, and could us some help. Where can I get a copy of Rdoc?

Hello all! I've got hardware error when trying to run photoshop 7 under wine 0.9.6 in freebsd 6.0. Here are console errors: fixme:actctx:QueryActCtxW stub! fixme:actctx:QueryActCtxW stub! fixme:actctx:QueryActCtxW stub! fixme:actctx:QueryActCtxW stub! fixme:font:WineEngRemoveFontResourceEx :stub fixme:actctx:QueryActCtxW stub! fixme:actctx:QueryActCtxW stub! fixme:palette:GetICMProfileA

I have Wine v1.0 and Linux Mint Elyssa with Adobe PS v7.01. PS loads up fine for a few seconds and then the docks all disapear. There are no layers,tools etc. How can I resolve this please? Everything else is fine just the docks are not there Many thanks Tony

Hi, Wine 0.9.17 user here having bad headaches with Photoshop menus... When choosing an option from the context menu or some other sorts of drop downs, the respective areas are not clickable even they are highlighted. Other thing would be that when I'm opening Blending Options, set some effects, then click OK, the tool windows is disappearing ... Could you advise on this matter, please?

I'm new(ish) to Linux and new to Wine. I have installed Photoshop 7. Mostly it appears to work fine, but the cursor disappears in some floating windows: Layers Channels Actions History Swatches It is fine in: Color Navigaotr Info Brushes File Browser This is a non-exhaustive list, but a few I have tested. The cursor still works (if I guess where it is then I can activate settings) -

I have Wine 20041019 and have done all the configuration with Wine tools. Then I Installed Photoshop 7 by executing ~/bin/dos then going to the cdrom drive and running the setup executable. The setup went fine and photoshop was installed. Then I simulated a windows reboot from wine tools. Then i again executed ~/bin/dos and went to the place where i Installed photoshop 7 and executed

Hi I just want to thank you for your great work with this incredible app! I just installed wine (sudo apt-get install wine) and then simply installed my Photoshop 7 (wine setup.exe): works flawless, can't get much easier :D Now with PS7 I'm feeling much more at home on my Xubuntu Linux! THX and keep up this awesome work! Miles

http://appdb.winehq.org/objectManager.php?sClass=version&iId=14318 it's rated gold but i can't install it [Laughing] i got ubuntu 8.10, i've tried before with wine 1.1.19 (last version) then i've noticed the advice of use 1.1.17 but i got the same problem [Question] i've downloaded from adobe site, no cracked or something else :P so i extract and wine work fine then when

Hi, I've just about got myself transferred from windowsXP to Linux (Mepis 3.3.1-1). I've got R 2.1.1, emacs, and ess running from the debian repositories. Of course, there is a hitch. I have a bit of C code in one of my personal functions. I have, apparently without problem, been able to compile it using R CMD SHLIB, but when I try to dyn.load it I get the following error: >

I am working with a function "foo" that explicitly dynamically loads a shared object library or "DLL", doing something like dyn.load("bar.so"). This is a debugging exercise so I make changes to the underlying Fortran code (yes, I acknowledge that I am a dinosaur) remake the DLL "bar.so" and then run foo again. This is all *without* quitting and

Hi, Most companies we work with, have 'designated' crisis management teams. These vary from the insignificant crisis', through to life-threatening crisis'. There is always an assigned emergency services contact, whose job it is in an emergency, to maintain communication with the emergency services. One of our corporate functions is crisis management - so we have to consider

Just got dovecot running inside MEPIS 3.3.2 SOHO (debian). I am impressed. It works really well and I am planning to move my mail away from my Win server and access the mail from dovecot using imap. I have copied some folders from my existing Outlook mail system into the imap mail server without any problems....so here is the dumb question: where are the mail files/folders stored on the MEPIS

Hello, In such cases, with C code, I call dyn.unload before loading the modified shared lib again. I don't know if this changed recently, but it used to be needed or else R wouldn't load the new lib. When I call dyn.unload followed by dyn.load I never had problems. (Or the other way around, call dyn.unload before modifying the C code.) Hope this helps, Rui Barradas On 3/1/2018 8:52

On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK Cc: stable at vger.kernel.org Cc: Amit Shah <amit.shah at redhat.com> Signed-off-by: Michael S. Tsirkin

On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK Cc: stable at vger.kernel.org Cc: Amit Shah <amit.shah at redhat.com> Signed-off-by: Michael S. Tsirkin

On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK This behaviour will break with hypervisors that assume spec compliant behaviour. It seems like a good idea to have