> Your response is diverging, rather than converging to a solution. And I > thought that I am suggesting a simple solution. I am sorry about that. > > So, here is partial response: > > If your desktop prints over the network, then if you copy the vBox as I > suggested should, in theory, solve the problem. > > If your desktop prints over USB and you setup vBox by creating new VM > using > a disk (.vdi) from the desktop - that is brand new setup. In such case, I > must have misunderstood your past references to working desktop as part of > the solution space.
The VM will take control of the USB port and talk to the printer directly in this case. You may need to tell the VM manager to assign the USB port to the VM and then release it when you are done. > > Given the time already spent on this problem and where we stand - How > about > packing your laptop, printer plus the router and bring the whole thing to > PLUG clinic? > > Hopefully, you would have your answers in one short afternoon rather than > making this into a multi-year project. > > As added bonus, we cold help you to break all the things properly and > permanently dramatically simplifying your future life! > > -Tomas > > > On Nov 6, 2017 4:22 PM, "Denis Heidtmann" <[email protected]> > wrote: > >> Tomas, >> >> Before I attempt to understand the details of your proposal, I want to >> clarify the current setup. The desktop host is connected to the printer >> via USB. The desktop network in VB is NAT. The laptop host >> communicates >> to the printer via the wireless router, not through the desktop. >> Wireless >> Direct in the printer is disabled. The current laptop guest was >> installed >> by copying the VDI from the desktop to the laptop. (I do not recall the >> details of that operation; I had help.) Both the desktop and laptop >> guest >> is windows 2000. >> >> Does the difference between the way the desktop (host) and the laptop >> (host) communicates to the printer matter, i.e., will the VM from the >> desktop when copied to the laptop still communicate to the printer >> properly? (It should be obvious, by my asking this question, that I do >> not >> understand how Virtual Box performs its magic.) >> >> If your answer to this question is yes, then I wonder if making a new VM >> instance in the laptop w/o removing the existing VM is possible and >> makes >> sense? Alternatively just removing and replacing the VM I think is >> reasonable--I think I have nothing unique in the laptop VM except the >> data, >> which is in a folder shared between the guest and host. (The shared >> folder >> in the desktop has a different name; I think that is one of the issues >> I >> had to deal with when I did the previous installation of the VM in the >> laptop.) >> >> Thanks for your continued willingness to concern yourself with this >> issue. >> >> -Denis >> >> On Mon, Nov 6, 2017 at 1:00 AM, Tom <[email protected]> >> wrote: >> >> > Hi Denis, >> > >> > I am having second thoughts about your problem. Some times, the >> easiest >> > thing is to leave the working stuff alone, working. >> > >> > You say that it works for you on your desktop. I assume that it is the >> > same W2k VM, right? >> > >> > If the above is true, it should be as simple as copying your VM setup >> > from the desktop to laptop and starting it. >> > >> > Here is how I would approach it: >> > * backup your existing ;aptop VM setup if you have any other VM >> already >> > configured on the laptop differently than on the desktop. You will >> > merge the differences later. >> > * stop vBox >> > * you need to cary over following directories/files in your home from >> > the laptop home dir: >> > rsync -a --progress desktop:VirtualBox\ VMs ./ >> > rsync -a --progress .config/VirtualBox .config/ >> > * start vBox and the W2k VM and it should work identical to desktop. >> > >> > If it does not still work you will need to check firewall on your >> > laptop, try NAT .... >> > >> > Hope it helps, Tomas >> > >> > On Sun, 2017-11-05 at 18:17 -0800, Denis Heidtmann wrote: >> > > The saga continues--- >> > > (The subject should be NOT printing from VB) >> > > >> > > It was suggested that in installing the printer from the Win2k guest >> > > I >> > > should give the port name of 9100. Did not help. (Note that this >> is >> > > the >> > > name, not the number. The number has on all recent attempts been >> > > 9100.) >> > > >> > > I have stumbled on a list of messages in a file accessed through >> > > control >> > > panel/administrative tools/computer management/system tools/event >> > > viewer/system Here is one that might mean something to those >> skilled >> > > in >> > > the art. I was asked what the error message was. This is all the >> > > detail I >> > > have been able to come up with. >> > > >> > > 11/3/2017 9:13:15 >> > > Printer hp deskjet 990c series was created. >> > > >> > > 11/3/2017 10:28:43 >> > > The document Test Page owned by Administrator failed to print. Win32 >> > > error >> > > code returned by the print processor: 3003 (0xbbb). >> > > >> > > Whenever I attempt to print I see this identical error, whether a >> > > test page >> > > or document. >> > > >> > > Note that I can ping the printer from the guest, so that hints to me >> > > that >> > > the issue is the installation of the printer in windows, not in the >> > > network. I have lost track of how many times I have deleted the >> > > printer >> > > and reinstalled. Note that this driver works from the windows2000 >> > > guest on >> > > my desktop. I also note that the printer worked before changing the >> > > desktop >> > > and the router, although I have had issues in the distant past, >> > > details of >> > > which my foggy head cannot recall. >> > > >> > > Is changing to NAT still a thing worth trying? >> > > >> > > -Denis >> > > _______________________________________________ >> > > PLUG mailing list >> > > [email protected] >> > > http://lists.pdxlinux.org/mailman/listinfo/plug >> > _______________________________________________ >> > PLUG mailing list >> > [email protected] >> > http://lists.pdxlinux.org/mailman/listinfo/plug >> > >> _______________________________________________ >> PLUG mailing list >> [email protected] >> http://lists.pdxlinux.org/mailman/listinfo/plug >> > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > perl -pe 's/^\s+//g' *.py _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
