As far as I know from the revision history of ArcaOS 5.0.2, there's a document in there......all the tools that are related - but I think MiniLVM, when you have a GPT disk in your system -And the disk utility is also fixed, it gives you a warning if there's a GPT.I think you can wipe the drive but other than that it won't do anything.So you should be safe, in theory.Well, in theory it will never get to that point, because when you start MiniLVM......and there is no VLAT sector, put there by the disk utility -But that will also not work, there is another safeguard because if LVM doesn't see a DLAT sector......it will automatically flag the disk as being corrupt in LVM's opinion.And since the disk utility cannot add a VLAT sector since it sees a GPT partition...... any edits you will do when exit LVM, and you try to save it, it will tell you it's a corrupted disk.So that should also be locked down.There's only a message on the screen.But up until some time ago you couldn't always scroll down on some systems......due to a bug in the installer and you didn't see that message.Can I ask something about that?In ArcaOS, if you are using peer networking, the shares are no longer part of the properties on any disk.If you go to a disk, and use Properties, you see Start sharing, Stop sharing, Update share, Manage access.These have been removed in ArcaOS. Is there a way to access that?That driver is some cases in the DOS$ services, pretty confusing......but that driver is used by some executables to reboot OS/2.No I mean, I disagree, I do the same in the reverse direction......I click up there to open up (...) whatever I do and whatever I need for command line stuff.And I need cmd.exe as a standard (...) and all these problems popping up randomly......because things were not designed to work with, for instance...the (...) /r command gives different data and some installers go "nah, I can't use that".I figured it out, and I looked at the sources at that time with Steve, from the DDK that he has......and this whole avalanche of switches will probably not help to address the issue.On 1.1 got a VVGA.SYS. But this is one of those - with the last of the drivers supported by SNAP......which didn't have DOS step-through implemented properly, ......and once you figured out you can actually run full screen on all of these......but for instance if you want to run (..) you can't .... away......you gotta actually open a DOS thing and have the commands in a window.One small problem about mice......if you connect them to a USB socket that is polling, ......if you connect them to the PS/1 socket that is interrupt based.But that's what I am telling, it's purely a hardware thing.There's by the way one other nasty thing that people should know...... when running SMOUSE in conjunction on a pretty modern system with ACPI.If the system is running in APIC mode, as in, you have more than 15 interrupts......on some laptops running SMOUSE will crash the system at startup......because it can't handle more than 15 interrupts for whatever oddball reason.So, it's another reason why on modern laptops -I think a trap was reported once on a T60 or T61 I think, it's pretty long ago......the crash would occur if you would install SMOUSEOr put it on the RAM-disk.I found that mine was never getting updated, and the problem was simply that......it would take long enough to make the link to the router, wireless, ......so that the delay time was insufficient, and the time of a minute was set to 12 hours, ......so it would startup, wait, couldn't make a connection and 12 hours later......it was already shutdown for the day so it never reset the time. So there's a setting for the turn-on delay......and I can set that to two minutes in stead of one minute, and the problem went away.One thing that is very, well not very easy with ClipView is adding extra lines.Which you have to go, Clip, Add, select a few lines, Clip, Add and it moves up, on the screen.The easy way is just to select the Lock box and if you only have one line you press the lock box,...you automate to the line underneath - you keep the lock boxes and immediately got it all setup as you want.Right, does it include a cursor? The mouse pointer?The standard (...) didn't.Because if you want something that also includes the mouse pointer, ......with PM camera, also (...) so if you want to have a -...for a particular reason a printscreen with a cursor showing pointing at something......for documentation, you can use PM camera.- You can also actually print the screen.It's not just a calendar, when you don't do anything else with it you end up with: a calendar.It has one known bug: if you have a week that begins on Sunday......and only has 4 lines like February, it goes nuts.Yeah right, you know, there's one year in the past when - "oh that's interesting"......but other than that it seems to works.Of course.