I think I remember it was 3.14. There's a winbraille 5, in fact, I
keep a copy of it on my flash drive for my index clients because we
sell a lot of basic-D and the driver cd for it is very buggy imho. I
don't know whether the everest supports winbraille 5 though, and I'm
not sure it would help in this case anyway, because we're not getting
the printer detected properly, and we're crashing the vm every time
the embosser gets plugged in, before we even get to he device driver
instalation.
Here are some more thoughts I had.
I'm sort'a in agreement with Alex, the one thing to do is to set the
everest up on the mac side and get it working. Then we'll know for
sure that it's a software issue, not a hardware issue. We pretty much
have it figured, but setting it up on the mac side has the added
benefit of actually being able to use the embosser til we get the
problem with the vm sorted... if we ever do.
Once that's done, try running a safer networking regalizer to clean
out your registry of bad or errant keys. Then see if you can find
your driver cache and clean it out, so it doesn't try installing a
corupt driver when you plug in the embosser.
Need I say, back up the vm if you value it in the slightest before
trying this stuff.
Best,
erik burggraaf
Certified Technician
Assistive Computing LTD Support and training
Sales department: 888-828-2445
Support and Training: 888-255-5194
Email: [email protected]
Website coming soon
On 9-Jan-09, at 11:56 PM, Simon Cavendish wrote:
Hello, Might it have something to do with the version of printing
software or firmware you use? Did you say you were running
winbraille 3.10?
On 10 Jan 2009, at 00:17, erik burggraaf wrote:
Hi, Well I can tell you what the meening of beef is, though it
won't help you. Beef seems to be the hexidesimal virtual ID for
the everest, but the everest doesn't seem to be being detected
properly. Notice that your lexmark 540, and your apple IR receiver
are both identified by name, but under device name for your
everest, it just says printer. Could it be that you have a
conflicting vid or pid? If you keyword search the log for beef and
0003 and see if any other devices are using those as vid and pid
numbers, that might tell us something. Other wise, all I'm getting
from that log is that the everest isn't being detected properly,
which we already knew.
Best,
erik burggraaf
Certified Technician
Assistive Computing LTD Support and training
Sales department: 888-828-2445
Support and Training: 888-255-5194
Email: [email protected]
Website coming soon
On 9-Jan-09, at 3:51 PM, william windels wrote:
Here I am again,
Erik, you where right, I mean that , if the printer is attached
before the virtual machine boots,
I have the possibility to enable the printer in the menu-item
"virtual macines" and then usb.
But, when I do this, a setup in windows is starting and after a
very short time, the system crashes and the virtual machine is
powered off itself in a abnormal way.
I have found the most recent logfile ans I see only a litle
differens between this printer and my lexmark normal printer:
part of logfile:
Jan 09 23:47:14.968: vmx| USB: Found device [name:Lexmark\ 510\
Series vid:043d pid:009f path:13/15/1/3 speed:full family:printer]
Jan 09 23:47:14.968: vmx| USB: Found device [name:Apple\ IR\
Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]
Jan 09 23:47:14.968: vmx| USB: Found device [name:Printer vid:beef
pid:0003 path:13/15/1/4 speed:full family:printer]
end of logfile
what is the meaning of beef?
is this perhaps important information to solve this problem?
thanx in advance!
best regards,
William
Op 9-jan-09, om 16:22 heeft william windels het volgende geschreven:
hmm, I can look for it further but the effective problem is that
you can not connect the printer without crashing.
So, you can also not press the button while the printer isn't
still connected.
best regards,
William
Op 9-jan-09, om 13:49 heeft erik burggraaf het volgende geschreven:
Heh man, this may sound stupid, but did you look for a button in
the vmware window that says connaisseurect index everest and
press it? Sometimes my hardware gets passed straight through to
the vm, and other times I have to kick start it that way.
Best,
erik burggraaf
Certified Technician
Assistive Computing LTD Support and training
Sales department: 888-828-2445
Support and Training: 888-255-5194
Email: [email protected]
Website coming soon
On 9-Jan-09, at 3:03 AM, william windels wrote:
Hello all,
I would like to install my everest brailleprinter on my mac.
Since I didn't find out how it was working on mac itself, I
tryed it under vmware fusion (windows xp pro).
I used winbraille 3.14
The problem is that windows and vmware don't give reaction
anymore when I plug in the printer into the mac after
installing winbraille and the driver succesfully.
It's the last driver available at the moment.
With the same cable and the same software, the everest works
fine on a windows pc.
We can't find any logfile in windows about that and also, my
lexmark printer works fine under mware.
Some experiences or suggestions are very welcome!
thanx alot,
best regards,
William Windels
