Hi Ky!
> KM> So turns out the BIOS date was munged up, but the asset tag in
> KM> Dell's form says 2016. Still pretty new by my lights, and has an
> KM> NVMe so quite snappy. I named it Pony. Everyone wants a pony,
> KM> right? :)
> Right! It's "Ky's Litle Pony"!
KM> LOL that's it.
Thought you might like that one!
> ...I wonder if the BIOS date was damaged
> because of a bad BIOS update or something to do with encryption: it was a
> business computer and so possibly using a key when communicating.
KM> Normally there's an asset date that's permanent, and a BIOS date
KM> that can change. Apparently the former got rewritten along with
KM> the latter.
OK -- I was thinking the BIOS date always stayed the same but then that
didn't make sense because BIOSs can be updated and that also changes the
BIOS date to reflect the revision date. ...I just don't spend enough
time staring at the BIOS screens!
...Changing that asset date probably isn't all that much work: it's
changing electron states, not like soldering wires, but still something
that seems to indicated a major error occurred some place as that's a
field normally not played with.
> KM> Now if I could get its Win10 to let the rest of the network SEE
> KM> it... everything is set correctly, shared and discoverable and
> KM> the super secret admin account activated, but still is only a
> KM> name on the network and refuses to let anyone else see its
> KM> precious files. I seem to recall I had this problem with
> KM> Fireball's Win10 after it was lately updated...
> Well, maybe my guess on why the munged BIOS date is why the files aren't
> being seen externally.
KM> No, this is a Recent-version-Win10 thing. Fireball's Win10 does
KM> it too.
OK -- you can tell I haven't been paying attention to Windows. ...As
for the files not being seen, appears this site may offer a solution:
http://woshub.com/network-computers-not-showing-windows-10/
...Huh: just realzed I had searched for "Windows 10 files not seen on
network" and the results can back for computers not being seen. Not the
same. guys! (Well, step one would be to see the computer, then step two
the files!)
KM> OTOH, it can see the linux box's files.
Linux makes things easy! ...Well, sometimes! <gg>
> KM> ... if I'm going to have network problems, why don't I install
> KM> linux instead? that way I could have the same network problems
> KM> but overall less stupidity.
> Works for me! Might be able to have a passageway between the possibly
> encryted Windows section and the Linux section (shared folder). (My
> guess is still encrypted, but worth the fun playing!)
KM> Not encrypted. It was a brand new install from the recovery
KM> partition. And it shows you if it's encrypted. It's not.
I've had icons/indicators display the opposite state but if Linux is
seeing the files without any problem pretty much indicates they're not
encrypled and Windows just isn't communicating properly. Seems to
indicate the link above might be the clue.
> KM> Oh, here's the latest. The God Mode (access every setting in one
> KM> place) shortcut now won't show a name, only the icon.
> "Use my name in vane and banishment!"
KM> God cannot be seen...
Reminded me of the cartoon panel of a living room, woman answers the
door and two missionaries ask "Have you found Jesus?". The living room
curtains are pushed out a bit and a pair of sandled feet are beneath.
> .. The roof of your mouth is more like a ceiling.
KM> I gotta use this line on the dentist. <g>
I've started printing out 'strange items of interest' for my 6-month
checkups. First one was a several-year-old toothpaste ad with a
casually-good-looking guy with two decent-looking ladies. He is missing
a front tooth. He's also missing an eyebrow (and he has dark hair) but
just about everyone misses that detail.
» BarryMartin3@ «
» @MyMetronet.NET «
... Home is where the @ is.
--- MultiMail/Win32 v0.47
■ wcECHO 4.2 ≈ ILink: The Safe BBS ■ Bettendorf, IA
--- QScan/PCB v1.20a / 01-0462
* Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)
|
