After I stopped every startup option in the vain hope of tryng to
resolve the black overlay on the desktop icons, I could no longer
print.
No surprise there,
I restored all services options that seemed appropriate or essential
and;
1) I could not access network shares (except those provided by
VBOXSVR; 2) Although my printers all showed up, every attrempt to
print returned an "err".
Suggestions would be welcome.
(Even the inevitable rude ones. I need a smile)
TIA, Alan
On Thu, 18 May 2023 20:36:43 +0100
pinnerite <pinnerite@gmail.com> wrote:
After I stopped every startup option in the vain hope of tryng to
resolve the black overlay on the desktop icons, I could no longer
print.
No surprise there,
I restored all services options that seemed appropriate or essential
and;
1) I could not access network shares (except those provided by
VBOXSVR; 2) Although my printers all showed up, every attrempt to
print returned an "err".
Suggestions would be welcome.
(Even the inevitable rude ones. I need a smile)
TIA, Alan
You have more problems than anyone I have ever seen. How's that for
being rude?
Have you rebooted your computer????
On Thu, 18 May 2023 20:36:43 +0100
pinnerite <pinnerite@gmail.com> wrote:
After I stopped every startup option in the vain hope of tryng to
resolve the black overlay on the desktop icons, I could no longer
print.
No surprise there,
I restored all services options that seemed appropriate or essential
and;
1) I could not access network shares (except those provided by
VBOXSVR; 2) Although my printers all showed up, every attrempt to
print returned an "err".
Suggestions would be welcome.
(Even the inevitable rude ones. I need a smile)
TIA, Alan
You have more problems than anyone I have ever seen. How's that for
being rude?
After I stopped every startup option in the vain hope of tryng to
resolve the black overlay on the desktop icons, I could no longer
print.
No surprise there,
I restored all services options that seemed appropriate or essential and;
1) I could not access network shares (except those provided by
VBOXSVR;
2) Although my printers all showed up, every attrempt to print
returned an "err".
pinnerite <pinnerite@gmail.com> wrote:
After I stopped every startup option in the vain hope of tryng to
resolve the black overlay on the desktop icons, I could no longer
print.
No surprise there,
I restored all services options that seemed appropriate or essential and;
1) I could not access network shares (except those provided by
VBOXSVR;
2) Although my printers all showed up, every attrempt to print
returned an "err".
Apparently you didn't keep a log of what changes you made trying to fix
the icon problem. Naughty naughty.
Restore from the image backup you [should have] made before putzing in
the registry, disabling startup programs, and disabling/removing
services. If you don't save backups before commiting major changes,
you've chosen to burn your bridges to get back where you started.
If you don't save backups before changes, you could try System Restore. Unlike an image backup, System Restore won't get you back to the exact
state as before. Sometimes it works, many times not. You may have to
walk back through multiple SR restore points to get back to one before
the the computer got fucked up.
pinnerite <pinnerite@gmail.com> wrote:
After I stopped every startup option in the vain hope of tryng to
resolve the black overlay on the desktop icons, I could no longer
print.
No surprise there,
I restored all services options that seemed appropriate or essential and;
1) I could not access network shares (except those provided by
VBOXSVR;
2) Although my printers all showed up, every attrempt to print
returned an "err".
Apparently you didn't keep a log of what changes you made trying to fix
the icon problem. Naughty naughty.
Restore from the image backup you [should have] made before putzing in
the registry, disabling startup programs, and disabling/removing
services. If you don't save backups before commiting major changes,
you've chosen to burn your bridges to get back where you started.
If you don't save backups before changes, you could try System Restore. Unlike an image backup, System Restore won't get you back to the exact
state as before. Sometimes it works, many times not. You may have to
walk back through multiple SR restore points to get back to one before
the the computer got fucked up.
Linux makes logging easy so that problems can more easily be
identified. (If you learn to interpret the log contents).
Windows being closed source makes that a bit trickier.
Since Alan is running a Win10 Guest virtual machine on a Linux Host
computer, all he has to do, is keep a copy of the container file,
to roll back to a certain state.
After I stopped every startup option in the vain hope of
tryng to resolve the black overlay on the desktop icons, I
could no longer print.
No surprise there,
I restored all services options that seemed appropriate or
essential and;
1) I could not access network shares (except those
provided by VBOXSVR; 2) Although my printers all showed
up, every attrempt to print returned an "err".
Suggestions would be welcome.
(Even the inevitable rude ones. I need a smile)
pinnerite <pinnerite@gmail.com> wrote in news:20230518203643.588e9b4c900ec02fa97564af@gmail.com:
After I stopped every startup option in the vain hope of
tryng to resolve the black overlay on the desktop icons, I
could no longer print.
No surprise there,
I restored all services options that seemed appropriate or
essential and;
1) I could not access network shares (except those
provided by VBOXSVR; 2) Although my printers all showed
up, every attrempt to print returned an "err".
Suggestions would be welcome.
(Even the inevitable rude ones. I need a smile)
Dump that VBox Win10 and buy a refurbed W10 box from NewEgg* for $125 that comes with a W10 Pro license, and most likely, much better performance than you
see under VBox (if it's hosted on that PC in your sig), as well as no more oddball
problems like this display driver issue, and whatever the last problem was (that I can't
remember).
(*If you're in the US or Canada. Else, whatever hardware/software outlet you buy gear
from that offers 'refurbed' deals, in your neck of the woods.)
Paul <nospam@needed.invalid> wrote:
Since Alan is running a Win10 Guest virtual machine on a Linux Host computer, all he has to do, is keep a copy of the container file,
to roll back to a certain state.
No mention by OP in this thread of using a VMM to run Windows in a VM.
He might've mentioned it in his prior posts, but then I would be
assuming a VM instead of a native install of Windows.
If his Windows VM is for experimentation, like to trial software, he
could just create a new VM for Windows as a guest; i.e., start from
scratch. He could create a new VM while leaving the old one around to
check if the new VM works okay.
For VMs, he may have to install the pass-through drivers in the VM to
get to the real hardware. Virtualbox has its Extension Pack (installed
in the host OS) and their Guest Additions (inside the VMs). I'd have to wander over to VMware's site to see what they call theirs.
Virtualbox allows snapshots for backups. Of course, if you schedule
backup in your host OS, that'll cover the virtual disk file for the VM,
but your backup program should support VSC (Volume Shadow Copy) if you
leave the VMs running (e.g., Virtualbox windowless mode).
https://www.techrepublic.com/article/how-to-use-snapshots-in-virtualbox/
On Fri, 19 May 2023 17:46:16 -0500
VanguardLH <V@nguard.LH> wrote:
Paul <nospam@needed.invalid> wrote:
Since Alan is running a Win10 Guest virtual machine on a Linux Host
computer, all he has to do, is keep a copy of the container file,
to roll back to a certain state.
No mention by OP in this thread of using a VMM to run Windows in a VM.
He might've mentioned it in his prior posts, but then I would be
assuming a VM instead of a native install of Windows.
If his Windows VM is for experimentation, like to trial software, he
could just create a new VM for Windows as a guest; i.e., start from
scratch. He could create a new VM while leaving the old one around to
check if the new VM works okay.
For VMs, he may have to install the pass-through drivers in the VM to
get to the real hardware. Virtualbox has its Extension Pack (installed
in the host OS) and their Guest Additions (inside the VMs). I'd have to
wander over to VMware's site to see what they call theirs.
Virtualbox allows snapshots for backups. Of course, if you schedule
backup in your host OS, that'll cover the virtual disk file for the VM,
but your backup program should support VSC (Volume Shadow Copy) if you
leave the VMs running (e.g., Virtualbox windowless mode).
https://www.techrepublic.com/article/how-to-use-snapshots-in-virtualbox/
Your comments are valid (I had not previously used snapshots).
The Tech Republic article is easy to read as well as being well
presented.
I have two VM: Win-10 and Win-XP. The latter has always been problem
free and is retained to support two large 16-bit programs and a Fujitsu cut-sheet scanner for which there is no usable Win-10 or Linux program.
It also runs pretty fast and is also a useful gauge as to whether a
fault lies with Win-10 or the underlying Linux host.
Win-10 was installed out of nevessiuty bevause essential commercial
programs for my business only run on Windows 7 or above.
Even at the best of times it has always executed at a snail's pace.
From 8 November 2022 no applicatioins were installed until 4 april 2023.
From 4 April the following were installed.
Amazon Kindle
TopUpTax (an essential professional program)
TaxCalc Discovery service (ditto)
PostgresSQL 9.4(x86)
Microsoft Visual C++ 2013 Redistributable (x86) -12...
TaxCalc (an essential professional program)
Mozilla Firefox (x86 en-GB)
MicrosftOneDrive
Adobe Acrobat (64-bit)
Microsoft Edge Webview2 Runtime
Miscrosoft Edge (installed 12 May 2023)
Microsoft Update Health Tools (installed 12 May 2023)
By choice I would not have installed the last four. Indeed after
considering your message, it is probablt time to take a snapshot,
uninstall them ans see what happens.
Thank you for taking the time.
Alan
On 5/19/2023 8:31 PM, DanS wrote:
pinnerite <pinnerite@gmail.com> wrote in
news:20230518203643.588e9b4c900ec02fa97564af@gmail.com:
After I stopped every startup option in the vain hope of
tryng to resolve the black overlay on the desktop icons,
I could no longer print.
No surprise there,
I restored all services options that seemed appropriate
or essential and;
1) I could not access network shares (except those
provided by VBOXSVR; 2) Although my printers all showed
up, every attrempt to print returned an "err".
Suggestions would be welcome.
(Even the inevitable rude ones. I need a smile)
Dump that VBox Win10 and buy a refurbed W10 box from
NewEgg* for $125 that comes with a W10 Pro license, and
most likely, much better performance than you see under
VBox (if it's hosted on that PC in your sig), as well as
no more oddball problems like this display driver issue,
and whatever the last problem was (that I can't remember).
(*If you're in the US or Canada. Else, whatever
hardware/software outlet you buy gear from that offers
'refurbed' deals, in your neck of the woods.)
Current generation of refurbs, gets you a quad core.
Previous generation (I have an Optiplex), it was dual core.
The quad core machines use DDR3. It's just possible
production of DDR3 memory has stopped (I was interested in
picking up some SODIMMs for the laptop, but production of
those stopped in Mar.2023, no stock of what I wanted).
You're over-thinking this. If one is using W10 under VBOX, they're not looking for huge frame-rate video, or anything high performance.
DanS <t.h.i.s.n.t.h.a.t@r.o.a.d.r.u.n.n.e.r.c.o.m> wrote:
You're over-thinking this. If one is using W10 under VBOX, they're not
looking for huge frame-rate video, or anything high performance.
We also don't know if the OP dedicated some CPU cores to the VM. ...
VanguardLH <V@nguard.LH> wrote:
DanS <t.h.i.s.n.t.h.a.t@r.o.a.d.r.u.n.n.e.r.c.o.m> wrote:
You're over-thinking this. If one is using W10 under VBOX, they're not
looking for huge frame-rate video, or anything high performance.
We also don't know if the OP dedicated some CPU cores to the VM. ...
https://www.alibabacloud.com/tech-news/virtualization/2fx-how-to-allow-for-more-cpu-cores-in-virtual-box
An OS inside VM should have as much system memory assigned to it as
would a native hardware setup to allow minimizing impact on
responsiveness. And the same for the number of cores available to the
OS in the VM. You give the same considerations to the VM as you would
for the native hardware. That means you should have twice the amount of
RAM and CPU cores available for the host OS since half of it will likely
go to the OS in the VM.
pinnerite <pinnerite@gmail.com> wrote:
After I stopped every startup option in the vain hope of tryng to
resolve the black overlay on the desktop icons, I could no longer
print.
No surprise there,
I restored all services options that seemed appropriate or essential and;
1) I could not access network shares (except those provided by
VBOXSVR;
2) Although my printers all showed up, every attrempt to print
returned an "err".
Apparently you didn't keep a log of what changes you made trying to fix
the icon problem. Naughty naughty.
Restore from the image backup you [should have] made before putzing in
the registry, disabling startup programs, and disabling/removing
services. If you don't save backups before commiting major changes,
you've chosen to burn your bridges to get back where you started.
If you don't save backups before changes, you could try System Restore. >Unlike an image backup, System Restore won't get you back to the exact
state as before. Sometimes it works, many times not. You may have to
walk back through multiple SR restore points to get back to one before
the the computer got fucked up.
VanguardLH <V@nguard.LH> wrote:
Apparently you didn't keep a log of what changes you made trying to
fix the icon problem. Naughty naughty.
On that point, is there a keystroke recorder for use in lengthy
adventures in software & installations, so that one can review the
past?
Peter Jason <pj@jostle.com> wrote:
VanguardLH <V@nguard.LH> wrote:
Apparently you didn't keep a log of what changes you made trying to
fix the icon problem. Naughty naughty.
On that point, is there a keystroke recorder for use in lengthy
adventures in software & installations, so that one can review the
past?
I use an ancient method employed long before computers existed, and even before electricity strung on wires (qualified to obviate electricity via lightning bolts or static shock). It's pen and paper. Of course, you
could go electronic with an editor, like Notepad on Windows, a note app
on your smartphone, or vim on Linux. No need to record keystrokes.
Just record your actions. You may have been weaned on computers, but I
bet you still used pen and paper not too long ago in elementary school.
pinnerite <pinnerite@gmail.com> wrote:
On Fri, 19 May 2023 17:46:16 -0500
VanguardLH <V@nguard.LH> wrote:
Paul <nospam@needed.invalid> wrote:
Since Alan is running a Win10 Guest virtual machine on a Linux Host
computer, all he has to do, is keep a copy of the container file,
to roll back to a certain state.
No mention by OP in this thread of using a VMM to run Windows in a VM.
He might've mentioned it in his prior posts, but then I would be
assuming a VM instead of a native install of Windows.
If his Windows VM is for experimentation, like to trial software, he
could just create a new VM for Windows as a guest; i.e., start from
scratch. He could create a new VM while leaving the old one around to
check if the new VM works okay.
For VMs, he may have to install the pass-through drivers in the VM to
get to the real hardware. Virtualbox has its Extension Pack (installed
in the host OS) and their Guest Additions (inside the VMs). I'd have to >> wander over to VMware's site to see what they call theirs.
Virtualbox allows snapshots for backups. Of course, if you schedule
backup in your host OS, that'll cover the virtual disk file for the VM,
but your backup program should support VSC (Volume Shadow Copy) if you
leave the VMs running (e.g., Virtualbox windowless mode).
https://www.techrepublic.com/article/how-to-use-snapshots-in-virtualbox/
Your comments are valid (I had not previously used snapshots).
The Tech Republic article is easy to read as well as being well
presented.
I have two VM: Win-10 and Win-XP. The latter has always been problem
free and is retained to support two large 16-bit programs and a Fujitsu cut-sheet scanner for which there is no usable Win-10 or Linux program.
It also runs pretty fast and is also a useful gauge as to whether a
fault lies with Win-10 or the underlying Linux host.
Win-10 was installed out of nevessiuty bevause essential commercial programs for my business only run on Windows 7 or above.
Even at the best of times it has always executed at a snail's pace.
From 8 November 2022 no applicatioins were installed until 4 april 2023. From 4 April the following were installed.
Amazon Kindle
TopUpTax (an essential professional program)
TaxCalc Discovery service (ditto)
PostgresSQL 9.4(x86)
Microsoft Visual C++ 2013 Redistributable (x86) -12...
TaxCalc (an essential professional program)
Mozilla Firefox (x86 en-GB)
MicrosftOneDrive
Adobe Acrobat (64-bit)
Microsoft Edge Webview2 Runtime
Miscrosoft Edge (installed 12 May 2023)
Microsoft Update Health Tools (installed 12 May 2023)
By choice I would not have installed the last four. Indeed after considering your message, it is probablt time to take a snapshot,
uninstall them ans see what happens.
Thank you for taking the time.
Alan
Try the System Restore first if you haven't used a backup program before inside the Win10 VM. Since this is a business computer, you should be running backups in the host OS (Linux), and they should be scheduled to eliminate the user doing the backups (since users are unreliable). If
so, those host OS backups should include the virtual disk file for the
VM, and you can try renaming the current VM file, and restore it from
your Linux backups to walk back until the problem disappears.
If your proposed uninstalls don't help, try rebooting Win10 in the VM
into its safe mode. You'll probably want "Safe Mode with Networking" if
any of the problems are with networking; for example, I don't know if
the printer is attached to the VM to use as a local printer to the Win10
OS inside the VM, or if the printer is on the network as its own node.
Safe mode will eliminate any non-essential services and startup programs
to provide a cleaner environ to test for the problems. Microsoft made
it more difficult to boot into safe mode, but there are plenty of online articles on the procedure.
After the uninstall, and if that doesn't help, I would look at what
config settings got changed by you for each of the programs you
installed into the Win10 VM to record them (unless a config file was available to save, or they have an export/import function) along with
all your data files for those programs. Save the data to storage, like
to a USB flash drive or USB HDD or even to optical disc. Then start
with a fresh install of Win10 into a new VM, install the Guest Add-ons
into the VM, take a snapshot, install one critical program, and test for
the problems. If no problems, take another snapshot, install another critical program, and test for problems. Repeat for each critical
program installation, but with a snapshot before the install, so you can
step back before after an install but encounter problems with it.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 09:28:36 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,336,272 |
