Printing /MYOB

[Russell Butler]

Hi all
I have a problem since installing MYOB(14.1) on wine on a gentoo AMD-64
box using kernel 2.6.20-gentoo-r7. I have Wine 1.0-rc1 installed into a
32-bit chroot.

MYOB runs acceptably, the only problem being selecting items in
sub-menus, which cannot be done at this stage. I can get around this by
removing everything from the "Forms" folder except my customised invoice
form.

However, I cannot print the invoice from MYOB and this is a
show-stopper. I have cups installed into the chroot and can print a test
page from notepad under wine, so it appears the problem is at a higher
level than that. Printer is a Samsung 4521 on a usb port. Unfortunately
the print dialogue doesn't offer a "Print to file" option as a work around.

I've attached a cups log output, if anyone can help. If there is some
other wine-specific logging, I am happy to look at that, but haven't
found any yet.

If I get this working I could blow away the vmware Windows install I use
currently and which is taking up several GB of space on my hard drive.

Thanks for any suggestions.

Russell
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cupslog_200805121555
Url: http://www.winehq.org/pipermail/wine-us ... chment.txt

[dimesio]

I'm by no means an expert in this, but from the cups log it looks to me like cups thinks it printed the job successfully. What exactly happens with your printer when you try to print--does anything come out at all? Does the light blink to indicate it's receiving data?

There is a cups backend called cups-pdf that prints to a PDF file. I've used it with Word 2003, so it definitely works Wine. That could be a workaround for you.

[qwertymn]

The following howto works in almost all cases for me:

1. Install cups-pdf

2. edit /etc/cups/cups-pdf.conf and put something like this:

Out ${HOME}/PDF

instead of

Out ${DESKTOP}

in the file (otherwise i got errors like 'permission denied')
Make sure you did 'mkdir ~/PDF' first of course

3. When the printer-dialog (in for example notepad or other app) opens, choose "Cups-pdf printer" , _DON'T_ choose "print to file" !!!, just hit 'OK' button, and you will find your pdf-file in ~/PDf with some kind of funny name.........

You can find this howto at
http://appdb.winehq.org/appview.php?iAppId=2549

[Russell Butler]

qwertymn wrote:

The following howto works in almost all cases for me:

1. Install cups-pdf

2. edit /etc/cups/cups-pdf.conf and put something like this:

Out ${HOME}/PDF

instead of

Out ${DESKTOP}

in the file (otherwise i got errors like 'permission denied')
Make sure you did 'mkdir ~/PDF' first of course

3. When the printer-dialog (in for example notepad or other app) opens, choose "Cups-pdf printer" , _DON'T_ choose "print to file" !!!, just hit 'OK' button, and you will find your pdf-file in ~/PDf with some kind of funny name.........

You can find this howto at
http://appdb.winehq.org/appview.php?iAppId=2549

Thanks a lot for this. I had installed cups-pdf, now I realise that it
was done under the 32-bit chroot install, only.

I can now print to cups-pdf, and a file is generated, but the page is
blank. I now realise I didn't say this in my original post, but printing
to the printer will produce a blank page. Hence the comment that the log
appears to generate a page.

Looks to me as though wine/MYOB is not translating the information into
postscript properly.

I tried installing PDF-Creator under wine (the Windows .exe) and it
comes up in the print dialogue, but just hangs, with no output.

Thanks for your help and interest

Russell

[dimesio]

Turns out there's an open bug for this: http://bugs.winehq.org/show_bug.cgi?id=6316.

You should add your info to that bug report.

[Russell Butler]

dimesio wrote:

Turns out there's an open bug for this: http://bugs.winehq.org/show_bug.cgi?id=6316.

You should add your info to that bug report.

Thanks dimesio I have done so, and voted.

Also made a comment on 9335 about menu selection. At least it confirms
still a problem in 1.0rc-1

Russell

[yonnie]

Several months ago, I installed MYOB and everything seemed to be working. Using F8 kde.

Now I'm getting similar results as the above complaints. I think this may have happened after the updater installed updates. Various tabs don't work in the MYOB and it's printing blank pages for receipts and invoices. Other printing from Myob seems to be ok. Using HP network printer and cups. Part of the problem is the MYOB printing setup won't allow me to choose print to plain paper, it wants to print to a myob form.

Other issues too! Wine uninstaller won't uninstall programs. removing the .wine directory doesn't seem to remove the software info from the file manager. Removing Wine with the add/remove software function, still leaves Wine in the file manager including the removed apps. Then using Synaptic or Yumex causes a failure during package reinstall.

We'd like to have our MYOB back, actually it's a little more urgent than that. Any idea as to when there might be a repair?

[Russell Butler]

yonnie wrote:

Several months ago, I installed MYOB and everything seemed to be
working. Using F8 kde.

Now I'm getting similar results as the above complaints. I think
this may have happened after the updater installed updates. Various
tabs don't work in the MYOB and it's printing blank pages for
receipts and invoices. Other printing from Myob seems to be ok.
Using HP network printer and cups. Part of the problem is the MYOB
printing setup won't allow me to choose print to plain paper, it
wants to print to a myob form.

Other issues too! Wine uninstaller won't uninstall programs.
removing the .wine directory doesn't seem to remove the software info
from the file manager. Removing Wine with the add/remove software
function, still leaves Wine in the file manager including the removed
apps. Then using Synaptic or Yumex causes a failure during package
reinstall.

We'd like to have our MYOB back, actually it's a little more urgent
than that. Any idea as to when there might be a repair?

HI yonnie

That's very interesting. Do you know what version of wine worked? I just
started trying on the 1.0-rc series, so I would be willing to go back
and try an earlier version if you could give me an idea about which one
functioned. At present I have it running in a vmware installation, but
would like to recover the space that requires.

Regards

Russell

[yonnie]

Over the last month I think two wine updates came in. I don't know if it was a core update or if they were other component updates. I know on the Fedora, there seems to be major updates every few days. I don't know which broke what. All I know for sure is that MYOB was working and now we can't use it. We have invoices to post and mail and can't.

[dimesio]

Several months ago, I installed MYOB and everything seemed to be working. Using F8 kde.

Now I'm getting similar results as the above complaints. I think this may have happened after the updater installed updates.

We'd like to have our MYOB back, actually it's a little more urgent than that. Any idea as to when there might be a repair?

Running a regression test would help: http://wiki.winehq.org/RegressionTestin ... %28test%29
Add the results to the bug report: http://bugs.winehq.org/show_bug.cgi?id=6316

[dimesio]

Wine uninstaller won't uninstall programs. removing the .wine directory doesn't seem to remove the software info from the file manager.

http://wiki.winehq.org/FAQ#head-9893ae5 ... af2e69b391

[yonnie]

Thanks,
I removed wine and then had a battle with re-installing. Finally had to login as root to do so. After wine re-install, menu's showed former programs still present, but are inoperable. Re-intalled MYOB still has same issues, spent most of last night trying to get the latest updates installed for wine and f8. Still no improvement. Then read about using spacebar after mouse selection. That only works for some tabs, not all. Still can't select for Myob to use plain paper instead of pre-printed forms, and I just get blank pages when trying to print invoices. I'm using myob plus 11, it's old and since the manual doesn't mention xp, I'm guessing it was pre-xp so using wine setting for 98 (xp setting didn't make any difference). Since the MYOB was a pita back when we first bought it and running real 98, we've never wanted to upgrade it. We're waiting for a good accounting program for Linux since we will never go back to windows. Meanwhile, we'd sure like to get it working with wine.

If it would help, we could send in a copy of it, that's if the cd will copy.

[yonnie]

Turns out there's an open bug for this: http://bugs.winehq.org/show_bug.cgi?id=6316.

You should add your info to that bug report.

I get a 6316: invalid bug report when trying to go there.
'6316.' is not a valid bug number nor an alias to a bug.

Please press Back and try again.

[austin987]

On Thu, Jun 19, 2008 at 12:04 PM, yonnie <[email protected]> wrote:

Turns out there's an open bug for this: http://bugs.winehq.org/show_bug.cgi?id=6316.

You should add your info to that bug report.

I get a 6316: invalid bug report when trying to go there.

Site's still a little funky after the slashdot+digg effect Tuesday with 1.0.

[vitamin]

On Thu, Jun 19, 2008 at 12:04 PM, yonnie <[email protected]> wrote:

Turns out there's an open bug for this: http://bugs.winehq.org/show_bug.cgi?id=6316.

You should add your info to that bug report.

I get a 6316: invalid bug report when trying to go there.

Site's still a little funky after the slashdot+digg effect Tuesday with 1.0.

How about one without <dot> at the end?
http://bugs.winehq.org/show_bug.cgi?id=6316

[yonnie]

What an eye!!

[spauldingsmails]

Is there any resolution in sight for this problem? I'm getting pretty desperate to get payslips in particular working under MyOB v17 (I'm having the exact same problem in the latest myob version).

Even a workaround would be great at this stage.

[Russell Butler]

spauldingsmails wrote:

Is there any resolution in sight for this problem? I'm getting pretty
desperate to get payslips in particular working under MyOB v17 (I'm
having the exact same problem in the latest myob version).

Even a workaround would be great at this stage.

Hi

On the basis that yonnie said he had it running under a previous version
of wine, I have been trying to do a regression test, with very limited
results thus far. I've set "git bisect good" to wine-0.9.30 which is
about 18 months old, in the hope that this will cover an appropriate
period, but no luck after the first couple of compiles, partly because I
forgot I had to give it a 'CC="ccache gcc -m32" ./configure --verbose'
on my amd64 system and spent a while working out why I got compiler errors.

I'll try again aver the next few days.

Yonnie, if you receive this, is there any way you can suggest about what
version of wine was working, just to speed up the testing?

Russell

[yonnie]

It's whatever was current release during March. I have no way of doing regression tests, nor determining which broke what. IMHO the kernel is a suspect too, and March was a lot of upgrades ago for F8. The target system (F8KDE) gets used for MYOB about once a week and printing invoices about once a month, it took awhile before we discovered the system was really broken, we had initially thought it was a settings error. It was when I tried installing MYOB onto the systems using F8(gnome) that I realized the problem may be more than a setting issue. I don't understand enough about Linux to perform regression errors using those code(s), it's beyond my skill-level. I'm just a Linux user who became extremely tired of Windows. Since we don't have a need for networking MYOB, I'm thinking of switching to the free version of Quasar, just hesitant over all the data that would have to be re-entered. It would be so much simpler if Wine would start working again.

[Russell Butler]

yonnie wrote:

It's whatever was current release during March. I have no way of
doing regression tests, nor determining which broke what. IMHO the
kernel is a suspect too, and March was a lot of upgrades ago for F8.
The target system (F8KDE) gets used for MYOB about once a week and
printing invoices about once a month, it took awhile before we
discovered the system was really broken, we had initially thought it
was a settings error. It was when I tried installing MYOB onto the
systems using F8(gnome) that I realized the problem may be more than
a setting issue. I don't understand enough about Linux to perform
regression errors using those code(s), it's beyond my skill-level.
I'm just a Linux user who became extremely tired of Windows. Since
we don't have a need for networking MYOB, I'm thinking of switching
to the free version of Quasar, just hesitant over all the data that
would have to be re-entered. It would be so much simpler if Wine
would start working again.

Thanks yonnie

I had thought it must have been a while ago, and had started regression
testing at 0.9.33 or so. That's about 18 months back. I'll bring my
testing forward to 0.9.53 as the"good" version - that's 5 months back,
and see if I can do any better.
Interestingly, I had reached 0.9.37 and MYOB runs much the same, and
still has the invoice printing problem.

I'll come back if I can find anything useful.

I'm actually tempted to shift the whole lot to gnucash, but don't have
enough accounting knowledge to be confident I worked out all the tax
implications

Russell

[yonnie]

I had forgotten to mention... really sorry, but could be a major clue. F6 had a printing issue with MYOB and so did the first several releases of F8. I didn't close out our XP system until I had MYOB fully functional with F8 and that was FEB/MAR time frame. One of the updates around end of Feb. started it (MYOB) working for us. Then I killed the last M$ system we had.

[Russell Butler]

yonnie wrote:

I had forgotten to mention... really sorry, but could be a major
clue. F6 had a printing issue with MYOB and so did the first several
releases of F8. I didn't close out our XP system until I had MYOB
fully functional with F8 and that was FEB/MAR time frame. One of the
updates around end of Feb. started it (MYOB) working for us. Then I
killed the last M$ system we had.

Well, I've tried regression testing without success, partly because I
don't know which version worked.

From what I've noted 0.9.42, 0.9.43, 0.9.44, 0.9.52, 0.9.55 and 0.9.57
have been tested as well as 1.0 to 1.1.

Looking at the win-git log I was very hopeful that 0.9.55 was the
working version, as it had a number of printer entries, and seemed about
right for yonnie's timing, but no go on my system, I'm afraid.

Russell

[Russell Butler]

yonnie wrote:

I had forgotten to mention... really sorry, but could be a major
clue. F6 had a printing issue with MYOB and so did the first several
releases of F8. I didn't close out our XP system until I had MYOB
fully functional with F8 and that was FEB/MAR time frame. One of the
updates around end of Feb. started it (MYOB) working for us. Then I
killed the last M$ system we had.

Yonnie

There is another thread just developed, and at least for the moment a
workaround for printing invoices at least.

If you open the invoice in the "Sales -Edit Service" window - basically
just select the invoice and click on it, you can do "Send to - Disk"
which will generate a pdf based on your invoice. If you save it in a
linux - accessible directory, you can then print it.

HTH

Russell