Subj : Re: What to do with a gia To : Barry Martin From : Ky Moffet Date : Mon Sep 21 2020 21:26:00 BARRY MARTIN wrote: > Hi Ky! > > > KM> Well do I remember the TV Zorro... Xorro is a Xeon. Now if they'd > > KM> named the CPU Zeon instead..... > > People would still mispronounce it! > KM> -on... > > Thinking the German 'achtung'! Nah, obviously not paying attention. > Could be. Half-recalling something about who was there first: if > Windows was there originally one thing happened but if Linux was there > first something else happened. Yeah, in the olden days Windows always had to be installed first, and oldest to newest. Now I'm not sure it makes any difference. > The Windows first rule didn't always work, though I am talking of > limited experiences over several years (so various version of Windows > and Ubuntu). Some refurbished computers here came with a Windows and it > got wiped out even though I tried to have it dual boot. I used to frequent a forum where people often griped about Windows suddenly failing to boot. In every case, they'd been dual-booting with linux. I call this "learning from others' misfortunes" and have not had a mixed-species boot since Argo's Red Hat/Win95 setup, installed in 1995 (eventually RH lost its password, which was "password" and wouldn't boot at all, and was made to go away. However Win95 remained solid for all the years until Argo was finally retired, end of 2011.) > KM> Yeah, especially when three partitions and three boot menu items > KM> have have named themselves "WINDOWS". Took several boots to > KM> untangle which was which. I knew the middle one was Server, but > KM> you couldn't tell by looking! > > _Which_ Windows?! Sort of reminds me of when I installed the snap > version of VLC Media player (default one didn't play some file but the > snap version did). Both default and snap had the little orange cone > icon, same label -- which one was which? Oh yeah, have had that sort of thing too.. which of several icons? Which drive was it on again?? > KM> Exactly. I could see it blowing off the video driver. But it had > KM> zero business going anywhere near GRUB. Mighta been something in > KM> the configuration manager that expected an OK at that point > KM> instead of a CANCEL, and left something open/unwritten... still > KM> had no business... > > Possible incomplete/incorrect programming. Bingo. This is the hazard of having unfinished features, which was like as not the root of the problem. > KM> Imagine the fun once the next version comes out... they've said > KM> Win10 will be the last version of Windows. Implying that 20 years > KM> after they first broached the idea (it's been around since the > KM> Win2K launch, and I saw this with my own eyes), they'll FINALLY > KM> get Windows to be a cloud service, not a local OS. Meaning > KM> everyone is locked into subscription mode, not only for the OS > KM> but perhaps also for data storage. Same thing Adobe and Autodesk > KM> have already done. > > Half-thought: OK, so my computer works fine when I am able to connect to > the web, like normal. So what happens when I'm not able to connect. > like during a power failure, or the WiFi is encoded or the WiFi is > broken? (I have a HP notebook and its internal option is intermittant > at best.) EXACTLY!!! And I'm like... no way in hell. At the aforementioned launch were some 1000 IT pros. During the presentation, they all developed identical angry frowns. (I was off to one side near the front and had a fine view of the audience.) > KM> Anyway, once that's a done deal, there'll be ZERO control over > KM> updates. You'll get the OS the cloud sends you, and like it. > > I tend to start bristling at that! Might be just my "New Hampshire 'Live > Free or Die' attitude", but some things you just don't tell me to do > without a darn good explanation I agree to. (I was raised in NH and > move to IA.) Yep. Being of the Westerner stripe, my reaction is, "Oh yeah? Try and make me." > KM> provide the official ISOs with less trouble. But none of those is > KM> the desired OEM-specific ISO, tho I've found a couple other OEM > KM> images floating around. > > OK -- I probably should have checked further -- it's the thought that > counts?! If only thinking could instantly install the OS of our choice, with all the desired features... I know! I'll call it Telepathy. > > Winter project: I'll have to go through to see what I have - not just > > RAM but some old daughterboards. ...Probably not that much of interest > > in the RAM Dep't: recalling a bunch of small capacity units. > KM> I dunno, I can't see as far as your parts box. > It's blocking the view of your camera?! ...For some reason reminds me It's that tall??! > of one of the LP guys at the store (how we got into this discussion I > have no idea!): he was talking to his girlfriend (video chat) late one > night, apparently forgot to hang up when he put his phone down to go to > bed. Discovered it was still on in the morning -- after he had changed > 'in full view'. She wasn't on/awake at the time but he was a little > embarrassed at the possibility. LIS, how that discussions started.... WHOOPS! > > > > KM> This one is my first. It needs the Storport patch from Microsoft, > > KM> and an OS-specific driver. Which worked fine on XP64, and not at > > KM> all on Win7. Holy crap, I've never seen Windows do an autorevert > > KM> like THAT before... cycled through a bunch of angry screens and > > KM> finally did a full system restore... it was VERY unhappy... Well, > > KM> we won't try THAT again!! > > So it's true: computers _do_ get mad! > KM> Or at least Windows does!! Never have I seen so many error > KM> screens without anything locking up. One could regard its full > KM> recovery as miraculous. > I guess!! You must live right! Or it fears my mighty hammer. Er, axe. > KM> I don't think I can set it manually, but being even a few pixels > KM> off correct aspect ratio would drive my eyes to drink. Weirdly, > KM> the setting it picks is in correct ratio. (16xx by 9xx. But not > KM> an even number.) > > I was initially thinking "16:9" so the "16xx:9xx" wasn't making sense. > Your pixel numbers are 16-hundred-something by nine hundred something. > 1600x900 is a 16:9 ratio ("High Definition Plus / HD+") -- > might be a little more (or less) to accomodate for over- or > underscanning. Methinks I'd rather not have it blowing off the driver, because who knows what that might do under the hood. > > Have read where there are problems with Hibernation. > KM> None of mine have any trouble with it. But it's been an issue > KM> with older laptops in particular. Does need proper hardware > KM> support. Shouldn't be a problem with anything from about a > KM> quad-core or later, tho. > > My Lenovo laptop is 'only' dual core. Which is basically the same chip, just didn't test as good and got set to two cores. Anything with more than one real core, I should have said. Hyperthreading is not real cores. Anyway it's the chipset that counts (same one supports duo or quad), and it shouldn't have a problem. > > > > Reminds be of the headaches I had with the install of Ubuntu 18.04 on > > > this system because of a faulty memory module! And didn't help this was > > > my first time trying to use UEFI so didn't know also needed a 'special' > > > partition. > > KM> Ouch. Yeah, one of those things we learn by deleting it. > > "This looks empty and I need the space." Oops! > KM> The empty space, it not workee! > But look at all that space I'll have when it does work again!! Just see if it lets you use it! One of the Dells has an oversized recovery partition, and I wound up putting all sorts of junk in there as storage... > KM> I have the HDs to do it, and now system with SAS support, and a > KM> 4-holer hotswap bay... so all the body parts are present, if > KM> scattered around the room. Whether I'll ever do anything > KM> more complicated than "let Windows do it" remains to be seen. > > Yes, I've semi-sorta collected the hardware as sales and interest > strikes me. Also considering using some old/small hard drives -- one > considering is JBOD-ing them together, another is keeping individual but > sort of like partitions on a big capacity drive ==> small backup would > go to a small hard drive. I make images of small drives and store them on a big drive. > > ..Hmm: the RPi option is sounding interesting: I have 5v/12v power > > supplies and a hard drive rack....... > KM> Well, there ya go! > > Wonder if I'll need that sequential start-up switch with all the hard > drives?! At least with iStarUSA (my preferred brand) the multi-bay external units do it automagically. That's the only reason they have circuitry at all. The single-bay units are just pass-through. > KM> I dunno VNC... but now I know who to ask. > > Wikipedia?! > Some bloke on a BBS. > KM> Dig up from the grave as the case was with this one... was > KM> supposedly dead. Not dead, just slow boot like a server. Happy > KM> birthday to me. > > It is rather fun when something that doesn't work can be fixed easily! Such as by turning it on! þ RNET 2.10U: ILink: Techware BBS þ Hollywood, Ca þ www.techware2k.com --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .