Yesterday, following disabling hibernation, I thought I had resolved
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in
the hopes of getting into Safe mode.
It is not promising.
On 7/3/2023 5:56 AM, pinnerite wrote:
Yesterday, following disabling hibernation, I thought I had resolved
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in
the hopes of getting into Safe mode.
It is not promising.
It helps if you tell people the brand and model of your computer. Go
find the user manual to figure out how to reset the computer. Some
computers use different key combinations at startup to go into the BIOS.
On Mon, 3 Jul 2023 06:22:55 -0400
😎 Mighty Wannabe ✅ <@.> wrote:
On 7/3/2023 5:56 AM, pinnerite wrote:
Yesterday, following disabling hibernation, I thought I had resolved every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in the hopes of getting into Safe mode.
It is not promising.
It helps if you tell people the brand and model of your computer. Go
find the user manual to figure out how to reset the computer. Some computers use different key combinations at startup to go into the BIOS.
My windows 10 is a virtual machine running on VirtualBox.
Anyway I got in via Safe Mode and closed down before trying again.
That started a cycle of BSODs and reboots with no improvement.
Thr reboots start assoon as i enter my PIN.
Eventually I found out how to stop the automatic reboots.
I am now going to see what happens now. :)
On Mon, 3 Jul 2023 16:45:31 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Mon, 3 Jul 2023 06:22:55 -0400Well I have had two normal reboots and it now seems stable.
😎 Mighty Wannabe ✅ <@.> wrote:
On 7/3/2023 5:56 AM, pinnerite wrote:My windows 10 is a virtual machine running on VirtualBox.
Yesterday, following disabling hibernation, I thought I had resolved
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in >>>> the hopes of getting into Safe mode.
It is not promising.
It helps if you tell people the brand and model of your computer. Go
find the user manual to figure out how to reset the computer. Some
computers use different key combinations at startup to go into the BIOS. >>>
Anyway I got in via Safe Mode and closed down before trying again.
That started a cycle of BSODs and reboots with no improvement.
Thr reboots start assoon as i enter my PIN.
Eventually I found out how to stop the automatic reboots.
I am now going to see what happens now. :)
You know, what really pisses me off is that Microsoft can jump to a
BSOD but cannot display the reason on the screen!
On Mon, 3 Jul 2023 16:45:31 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Mon, 3 Jul 2023 06:22:55 -0400Well I have had two normal reboots and it now seems stable.
😎 Mighty Wannabe ✅ <@.> wrote:
On 7/3/2023 5:56 AM, pinnerite wrote:My windows 10 is a virtual machine running on VirtualBox.
Yesterday, following disabling hibernation, I thought I had resolved
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in >>>> the hopes of getting into Safe mode.
It is not promising.
It helps if you tell people the brand and model of your computer. Go
find the user manual to figure out how to reset the computer. Some
computers use different key combinations at startup to go into the BIOS. >>>
Anyway I got in via Safe Mode and closed down before trying again.
That started a cycle of BSODs and reboots with no improvement.
Thr reboots start assoon as i enter my PIN.
Eventually I found out how to stop the automatic reboots.
I am now going to see what happens now. :)
You know, what really pisses me off is that Microsoft can jump to a
BSOD but cannot display the reason on the screen!
On Mon, 3 Jul 2023 16:45:31 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Mon, 3 Jul 2023 06:22:55 -0400
😎 Mighty Wannabe ✅ <@.> wrote:
On 7/3/2023 5:56 AM, pinnerite wrote:
Yesterday, following disabling hibernation, I thought I had resolved every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows" near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in the hopes of getting into Safe mode.
It is not promising.
It helps if you tell people the brand and model of your computer. Go
find the user manual to figure out how to reset the computer. Some computers use different key combinations at startup to go into the BIOS.
My windows 10 is a virtual machine running on VirtualBox.
Anyway I got in via Safe Mode and closed down before trying again.
That started a cycle of BSODs and reboots with no improvement.
Thr reboots start assoon as i enter my PIN.
Eventually I found out how to stop the automatic reboots.
I am now going to see what happens now. :)
Well I have had two normal reboots and it now seems stable.
You know, what really pisses me off is that Microsoft can jump to a
On 7/3/23 12:13, this is what pinnerite wrote:
You know, what really pisses me off is that Microsoft can jump to aI always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.
BSOD but cannot display the reason on the screen!
Yesterday, following disabling hibernation, I thought I had resolved
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in
the hopes of getting into Safe mode.
It is not promising.
On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:
On 7/3/23 12:13, this is what pinnerite wrote:
You know, what really pisses me off is that Microsoft can jump to aI always thought the BSOD had a reason down at the bottom. A bit
BSOD but cannot display the reason on the screen!
obtuse, maybe too techy but there.
It's also captured in Event Viewer, as well as being visible in apps
such as Nirsoft's BlueScreenView. Both of those methods are especially
handy for people who configure their Windows systems to automatically
reboot when they encounter a BSOD.
On 7/3/2023 12:13 PM, pinnerite wrote:
On Mon, 3 Jul 2023 16:45:31 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Mon, 3 Jul 2023 06:22:55 -0400Well I have had two normal reboots and it now seems stable.
😎 Mighty Wannabe ✅ <@.> wrote:
On 7/3/2023 5:56 AM, pinnerite wrote:My windows 10 is a virtual machine running on VirtualBox.
Yesterday, following disabling hibernation, I thought I had resolved >>>>> every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in >>>>> the hopes of getting into Safe mode.
It is not promising.
It helps if you tell people the brand and model of your computer. Go
find the user manual to figure out how to reset the computer. Some
computers use different key combinations at startup to go into the BIOS. >>>>
Anyway I got in via Safe Mode and closed down before trying again.
That started a cycle of BSODs and reboots with no improvement.
Thr reboots start assoon as i enter my PIN.
Eventually I found out how to stop the automatic reboots.
I am now going to see what happens now. :)
You know, what really pisses me off is that Microsoft can jump to a
BSOD but cannot display the reason on the screen!
Don't expect a Windows OS running in a virtual box to behave 100% the same as in a real Windows hardware box. Windows computer is so cheap these days, you are wasting your time and torturing yourself with a virtual box.
Yesterday, following disabling hibernation, I thought I had resolved
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in
the hopes of getting into Safe mode.
It is not promising.
Can you post *where* that feature (do (not) reboot after a BSOD) is
set?
Yesterday, following disabling hibernation, I thought I had resolved<snip>
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
Frank Slootweg <this@ddress.is.invalid> wrote:
Can you post *where* that feature (do (not) reboot after a BSOD) is
set?
C:\Windows\System32\sysdm.cpl
Advanced tab -> Startup and Recovery
Under System Failure, deselect the "Automatically restart" option.
Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
The last copy that "just works".
But I don't want to dissuade Alan. The more experiments, the merrier.
We might discover how to tame the damn thing.
Paul
On Mon, 3 Jul 2023 18:40:32 -0400
Paul <nospam@needed.invalid> wrote:
//
Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, forI am using V7 of Virtualbox. (7.0.8) It has a one irritant.
stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
The last copy that "just works".
But I don't want to dissuade Alan. The more experiments, the merrier.
We might discover how to tame the damn thing.
Paul
I also run Windows XP under it. It is rock solid.
I don't run more more than one VM at a time for obvious reasons.
Last night I left an update 21H2 running (for the third time).
When I checked this morning I had a BSOD.
After rebooting Win 10 informed me that it was undoing something.
After rebooting again I was able to get some work done.
I finally decided to uninstall anything that was installed prior to the instability, including the latest updates.
After rebooting it then reported that it was making repairs!
Eventually it came up. I caried on working and then left the machine
alone for a bit. When I got back, another BSOD.
I think I made a mistake in not turning off automatic updates.
Every time I try to uninstall an update Windows reinstalls ut.
Right now it froze and I was forced to reset it.
Ot is now happ;lily telling me that it is "Getting Windows ready. Don't
turn off your computer".
...and then crashed with a BSOD!
So, next to start in Safe Mode. Hold down shift and click start.
An hour later and I still have a black square!
More to follow. :(
Alan
On Mon, 3 Jul 2023 18:40:32 -0400
Paul <nospam@needed.invalid> wrote:
//
Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
The last copy that "just works".
But I don't want to dissuade Alan. The more experiments, the merrier.
We might discover how to tame the damn thing.
Paul
I am using V7 of Virtualbox. (7.0.8) It has a one irritant.
I also run Windows XP under it. It is rock solid.
I don't run more more than one VM at a time for obvious reasons.
Last night I left an update 21H2 running (for the third time).
When I checked this morning I had a BSOD.
After rebooting Win 10 informed me that it was undoing something.
After rebooting again I was able to get some work done.
I finally decided to uninstall anything that was installed prior to the instability, including the latest updates.
After rebooting it then reported that it was making repairs!
Eventually it came up. I caried on working and then left the machine
alone for a bit. When I got back, another BSOD.
I think I made a mistake in not turning off automatic updates.
Every time I try to uninstall an update Windows reinstalls ut.
Right now it froze and I was forced to reset it.
Ot is now happ;lily telling me that it is "Getting Windows ready. Don't
turn off your computer".
...and then crashed with a BSOD!
So, next to start in Safe Mode. Hold down shift and click start.
An hour later and I still have a black square!
More to follow. :(
Alan
On 7/6/2023 9:01 AM, pinnerite wrote:
On Mon, 3 Jul 2023 18:40:32 -0400
Paul <nospam@needed.invalid> wrote:
//
Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
The last copy that "just works".
But I don't want to dissuade Alan. The more experiments, the merrier.
We might discover how to tame the damn thing.
Paul
I am using V7 of Virtualbox. (7.0.8) It has a one irritant.
I also run Windows XP under it. It is rock solid.
I don't run more more than one VM at a time for obvious reasons.
Last night I left an update 21H2 running (for the third time).
When I checked this morning I had a BSOD.
After rebooting Win 10 informed me that it was undoing something.
After rebooting again I was able to get some work done.
I finally decided to uninstall anything that was installed prior to the instability, including the latest updates.
After rebooting it then reported that it was making repairs!
Eventually it came up. I caried on working and then left the machine
alone for a bit. When I got back, another BSOD.
I think I made a mistake in not turning off automatic updates.
Every time I try to uninstall an update Windows reinstalls ut.
Right now it froze and I was forced to reset it.
Ot is now happ;lily telling me that it is "Getting Windows ready. Don't turn off your computer".
...and then crashed with a BSOD!
So, next to start in Safe Mode. Hold down shift and click start.
An hour later and I still have a black square!
More to follow. :(
Alan
In VM land, you boot the Win10 DVD image (.iso) and
use Troubleshooting instead of installing Windows. Select
the Command Prompt window option.
There isn't a particular reason this would be necessary,
but you can do this if you want.
chkdsk /f C:
If you do this, you can verify C: is the OS disk in that environment.
cd /d c: # an explicit, absolute-path-change-directory
dir # list visible files
dir /ah # list hidden files, to make sure you're on an OS partition for C:
DISM /image:c:\ /cleanup-image /revertpendingactions
That last command, says whatever update is in-flight, to reverse it.
Anything which is in the middle of installing, reverts itself.
After you exit the Command Prompt
exit
you should be back in DVD Troubleshooting options and Shut Down
should be an option.
After the VM is shut down, you can go to settings and remove the
DVD in Settings (tell it to not use the ISO).
*******
You could use InControl, to set the OS version to 21H2. That would
be, to prevent 22H2 from coming in. The InControl program can also
release the control, when you're satisfied it is safe for the VM to
proceed. The thing is, W10 21H2 won't be supported forever, and
W10 22H2 may be the last version with support right to the end of
2025.
http://al.howardknight.net/?STYPE=msgid&MSGI=%3Cu7ckf9%2411dkk%241%40dont-email.me%3E
There is also the button to punch, in Settings : Update/Security
and Windows Update settings, to delay updates for seven days.
That might stop minor updates, like a Patch Tuesday.
The program "winver.exe" , tells you what current version and
patch level you're at.
*******
Also, when you have a moment, in your host OS, give me a
inxi -F
copy and paste the output. I want to see what your host has
for hardware.
My Ubuntu has VirtualBox 6.1.38 on it, but I can run a
different version for test. This is the inxi -F on the
Test Machine.
bullwinkle@TUNAFISH:~$ inxi -F
System:
Host: TUNAFISH Kernel: 5.15.0-76-generic x86_64 bits: 64
Desktop: GNOME 42.5 Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish) Machine:
Type: Desktop Mobo: ASUSTeK model: P9X79 v: Rev 1.xx
serial: <superuser required> BIOS: American Megatrends v: 4608
date: 12/24/2013
CPU:
Info: 6-core model: Intel Core i7-4930K bits: 64 type: MT MCP cache:
L2: 1.5 MiB
Speed (MHz): avg: 1720 min/max: 1200/3900 cores: 1: 1240 2: 1974 3: 1896
4: 1269 5: 1753 6: 1262 7: 1808 8: 1912 9: 2036 10: 2310 11: 1279 12: 1903
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 515.105.01
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
gpu: nvidia resolution: 1280x1024~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
v: 4.6.0 NVIDIA 515.105.01
Audio:
Device-1: Intel C600/X79 series High Definition Audio driver: snd_hda_intel
Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel
Device-3: Philips s SAA7164 driver: saa7164
Sound Server-1: ALSA v: k5.15.0-76-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel 82579V Gigabit Network driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 40:16:7e:a8:94:0e
IF-ID-1: virbr0 state: down mac: 52:54:00:fa:0f:51
Drives:
Local Storage: total: 931.51 GiB used: 179.99 GiB (19.3%)
ID-1: /dev/sda vendor: Western Digital model: WD1003FZEX-00K3CA0
size: 931.51 GiB
Partition:
ID-1: / size: 314.18 GiB used: 179.99 GiB (57.3%) fs: ext4 dev: /dev/sda2 Swap:
ID-1: swap-1 type: file size: 1024 MiB used: 0 KiB (0.0%) file: /swapfile Sensors:
System Temperatures: cpu: 25.0 C mobo: N/A gpu: nvidia temp: 34 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 37%
Info:
Processes: 335 Uptime: 2m Memory: 62.73 GiB used: 1.85 GiB (2.9%)
Shell: Bash inxi: 3.3.13
bullwinkle@TUNAFISH:~$
Paul
On 7/6/2023 9:01 AM, pinnerite wrote:
On Mon, 3 Jul 2023 18:40:32 -0400
Paul <nospam@needed.invalid> wrote:
//
Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, forI am using V7 of Virtualbox. (7.0.8) It has a one irritant.
stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
The last copy that "just works".
But I don't want to dissuade Alan. The more experiments, the merrier.
We might discover how to tame the damn thing.
Paul
I also run Windows XP under it. It is rock solid.
I don't run more more than one VM at a time for obvious reasons.
Last night I left an update 21H2 running (for the third time).
When I checked this morning I had a BSOD.
After rebooting Win 10 informed me that it was undoing something.
After rebooting again I was able to get some work done.
I finally decided to uninstall anything that was installed prior to the instability, including the latest updates.
After rebooting it then reported that it was making repairs!
Eventually it came up. I caried on working and then left the machine
alone for a bit. When I got back, another BSOD.
I think I made a mistake in not turning off automatic updates.
Every time I try to uninstall an update Windows reinstalls ut.
Right now it froze and I was forced to reset it.
Ot is now happ;lily telling me that it is "Getting Windows ready. Don't turn off your computer".
...and then crashed with a BSOD!
So, next to start in Safe Mode. Hold down shift and click start.
An hour later and I still have a black square!
More to follow. :(
Alan
You are a masochist. Why don't you just buy a new, cheap Windows box
with the latest legal Windows OS already installed?
chkdsk /f C:
If you do this, you can verify C: is the OS disk in that environment.
cd /d c: # an explicit, absolute-path-change-directory
dir # list visible files
dir /ah # list hidden files, to make sure you're on an OS partition for C:
DISM /image:c:\ /cleanup-image /revertpendingactions
That last command, says whatever update is in-flight, to reverse it. Anything which is in the middle of installing, reverts itself.
After you exit the Command Prompt
Thanks Paul,
chkdsk /f C:
I ran chkdsk twice early on.
If you do this, you can verify C: is the OS disk in that environment.
cd /d c: # an explicit, absolute-path-change-directory >>>
dir # list visible files
dir /ah # list hidden files, to make sure you're on an OS partition for C:
The next commands seem to presume that I can access a command line while other user initiated processes are running. I cannot do that while an update is running.
By the way I have managed to stop updates until I eliminate the problem.
DISM /image:c:\ /cleanup-image /revertpendingactions
That last command, says whatever update is in-flight, to reverse it.
Anything which is in the middle of installing, reverts itself.
After you exit the Command Prompt
Regards, Alan
On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:
On 7/3/23 12:13, this is what pinnerite wrote:
You know, what really pisses me off is that Microsoft can jump to aI always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.
BSOD but cannot display the reason on the screen!
It's also captured in Event Viewer, as well as being visible in apps
such as Nirsoft's BlueScreenView. Both of those methods are especially
handy for people who configure their Windows systems to automatically
reboot when they encounter a BSOD.
On Mon, 03 Jul 2023 14:04:24 -0500
Char Jackson <none@none.invalid> wrote:
On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:
On 7/3/23 12:13, this is what pinnerite wrote:
You know, what really pisses me off is that Microsoft can jump to aI always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.
BSOD but cannot display the reason on the screen!
It's also captured in Event Viewer, as well as being visible in apps
such as Nirsoft's BlueScreenView. Both of those methods are especially handy for people who configure their Windows systems to automatically reboot when they encounter a BSOD.
A kid two doors away told me about the Event Viewer too while his dog
was licking me to death.
Apparently the culpret is VBoxDispD3D.dll
However updates may have taken care of it.
Although my desktop icons have disappeared again (the text remains), it
seems to be stable.
Thanks, Alan
On Wed, 12 Jul 2023 15:25:43 +0100
pinnerite <pinnerite@gmail.com> wrote:
On Mon, 03 Jul 2023 14:04:24 -0500
Char Jackson <none@none.invalid> wrote:
On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:
On 7/3/23 12:13, this is what pinnerite wrote:
You know, what really pisses me off is that Microsoft can jump to aI always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.
BSOD but cannot display the reason on the screen!
It's also captured in Event Viewer, as well as being visible in apps
such as Nirsoft's BlueScreenView. Both of those methods are especially
handy for people who configure their Windows systems to automatically
reboot when they encounter a BSOD.
A kid two doors away told me about the Event Viewer too while his dog
was licking me to death.
Apparently the culpret is VBoxDispD3D.dll
However updates may have taken care of it.
Although my desktop icons have disappeared again (the text remains), it
seems to be stable.
Thanks, Alan
As usual I spoke (wrote) too soon.
Despite setting up shared directories in virtualbox and in samba (belt
and braces), under Windows 10 the shared folders are inaccessible yet
the XP VM has no trouble.
(Except it cannot my cut-sheet scanner any more.
Fortunately the Linux host can.
:(
Yesterday, following disabling hibernation, I thought I had resolved
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in
the hopes of getting into Safe mode.
It is not promising.
--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8
On Mon, 3 Jul 2023 10:56:35 +0100
pinnerite <pinnerite@gmail.com> wrote:
Yesterday, following disabling hibernation, I thought I had resolvedThis did get resolved after uninstalling several resently installed items and persisting with updates but it remained unusable because it could not communicate with its host.
every problem that had been plagfuing me for several weeks.
This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.
As I write I have tried restarting it while holding down the F8 key in
the hopes of getting into Safe mode.
It is not promising.
In the end, I rebuilt the host (Linux Mint 21.1) and copied the whole Windows 10 folder (nearly 100Gb) and it is all working now.
Regards, Alan
--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8
This did get resolved after uninstalling several resently
installed items and persisting with updates but it remained
unusable because it could not communicate with its host.
In the end, I rebuilt the host (Linux Mint 21.1) and copied the
whole Windows 10 folder (nearly 100Gb) and it is all working now.
Regards, Alan
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 10:23:14 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,336,334 |
