I went down the "install on Windows and copy across" path. _Almost_ all of MYOB gets installed in its own directory, just a couple of ini files in the Windows dir., but it did need a Windows dll which I had to copy across as well.
Anyway I got it started with several repeats of an error message, but it still isn't fully there yet, so I guess I might have to fork out for win4lin. On Wed, 2004-07-14 at 11:49, James Gregory wrote: > On Tue, 2004-07-13 at 22:25 +1000, Howard Lowndes wrote: > > This was visited in the archives about 3 years ago with subscribers > > saying that it works, but I don't believe them. I can't even get it to > > install. > > Well, the version from 3 years ago probably does work. > > I had to visit this problem recently at work. I'll tell you where I'm > at. > > First of all, the installshield stuff is very difficult to persuade to > work (there's a million workarounds but I personally don't have the > patience). In the case of MYOB in particular this isn't too problematic > though because MYOB installs almost all of its files in its own > directory -- it doesn't leave garbage throughout /winnt. > > I suggest installing on a windows box and copying it over. I use the > "find files created in the last day" thing to locate all the files it > created. > > > OK, so perhaps I should be trying to use an installed system, but how do > > I know what files I need in my various parts of the wine filesystem? > > The find files thing works well. The other option is to use a dependency > walker. There's a well known one, but I don't remember what it's called. > > I guess I may be at an advantage on this because I only boot my windows > machine for doing this kind of thing -- files created in the last day > were *definitely* from the installer for me. > > > > > I really need to get this one going as it is the last link in getting a > > client totally off M$ and onto Linux 100%. Everything else is doable > > with OS apps except for MYOB (I know about SQL-Ledger, I use it myself, > > but I am trying to make the change appear as minimal to the client as > > possible). > > Ok. So I managed to get MYOB PowerPay to work relatively easily. That's > the cut down version that just does payroll. I have not yet been able to > get the current version of MYOB Premier to work. It looks a lot like > PowerPay uses an older version of the MYOB "engine". If you can run a > slightly older version of MYOB (I don't know if this is possible in your > circumstances), you'll likely improve your chances of success > considerably. > > Which version do you need to run? I strongly suggest copying a windows > installation and see what errors you get then. If you can do that and > post to the list, I'll take a look and see if I can suggest anything. > There's some traces that would be helpful in debugging as well, but see > how you go. > > HTH (though it probably didn't) > > James. -- Howard. LANNet Computing Associates; Your Linux people <http://www.lannetlinux.com> ------------------------------------------ "When you just want a system that works, you choose Linux; when you want a system that just works, you choose Microsoft." ------------------------------------------ "Flatter government, not fatter government; Get rid of the Australian states." -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
