The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Thanks! I already have been practicing on a piece of cardboard which I decoratedbwith some lines of rivets, some panels and of cours a spray of the Huey's green paint. My results are not always subtle enough yet, so I guess I need some more practice. Simple things, like that pin wash of the doors yesterday already go quite well and also bringing out the Huey's 15+ meters of rivets with a brownish wash should be no problem.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
I reinstalled my laptop, did a complete format of all my partitions and created them anew.
The first thing that I thought was really weird is that the installer told me to sign in with my ex-employers work account (I bought this laptop from them).
I mean, how would a fresh install know this is a laptop from my ex-employer?
I never had any problems with this laptop, it all started when it was reinstalled a little over a week ago.
It just doesn't boot correctly.
The first time I boot nothing happens, I just see black screen and after a minute or so the keyboard lights up until it goes idle.
After turning it off and on again the Dell logo shows up and... Nothing happens again.
After turning it off and on a second time the Dell logo shows up again and after way too many seconds a spinning icon appears and Windows starts up (total startup time about two mintes!).
And now, after a clean install, it still does that!
It could be a hardware problem, although the hardware diagnostic tool said everything was fine.
Besides, the hardware didn't change, it just got reinstalled.
But it doesn't seem to be a software problem either as it was wiped twice and it somehow persists over multiple boots.
I just don't understand how it boots differently three times, but always in that same pattern!?
When it's booted everything works fine.
Even a regular restart (without turning it off completely) works fine, about 10 seconds boot time.
This is by far the weirdest issue I've ever encountered and it taught me one thing: I know absolutely nothing about computers
The ultimate question, of course, what's wrong and how can I solve it?
Go into the BIOS, and ensure that it has no odd settings (BIOS password, device boot order, etc.)
Get a thumb drive (8 GB or more)
Go to another Windows 10 computer and download the Windows Media Creator
Run this, and create a Windows 10 installation thumb drive
Make sure that you download a version for which you have a license (e.g. don't download Windows Pro if your license is for Windows Home)
Use this to boot your computer
Install Windows from scratch (including a format and repartition of the hard drive)
Open File Explorer, Right-click on "This PC" in the left-hand window, and select "Properties".
Scroll to the bottom of the window. On the right, you will see an option to change the product key. Click this, and enter your new product key
This should overwrite your employer's record of Windows in the BIOS and in Microsoft's servers.
Lastly, go to Dell's site, download their tool that updates all Dell drivers, and run that to get their latest stuff.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
On laptops' hard drives, there are often hidden partitions; could it be possible that you only wiped partition(s) which could be seen?
I'm using Ultimate Boot CD when I want to have a rather precise clue about how a disk has been partitioned. Maybe you could gain some knowledge about your issue from it?
Been there done that - bought a grey market licence to get around w10s draconian licencing. I'd bet the hard disk id is registered with MS somewhere and it references that to determine the owner. I would consider getting a new SSD as your primary drive, that may allow you to do a clean install.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
Or press the "Go" button, then go and start making coffee/grab a newspaper and read a paragraph and a half of a story that interests you/look at a Rubik's cube, twist it twice, then put it down/anything else that will keep you busy for this Huge amount of time.
It's two minutes. I imagine that you might have somewhat more pressing issues to spend your time on.
I wanna be a eunuchs developer! Pass me a bread knife!
The problem isn't those two minutes, it's that it first fails booting at all twice and then takes about six times longer to boot than it should.
I could ignore it now and wait until it completely fails on me when I'm doing a demo for a potential customer or I could spend some time now to solve this issue and save me a lot of frustration and haul in that customer later.
OK, having taken the time to read all the details (which takes longer than two minutes -- I could boot a computer in that time!) I'm now wondering why you are hoping that reinstalling windows will fix a problem that is arising before windows loads.
Take a look at your BIOS settings.
In particular, check the BIOS version, and download and flash the latest if it's not.
If it is the latest version, just go through all the settings (with a guide open on another machine), paying special attention to HDD and memory settings.
There's also the possibility that you might need an older version of the BIOS, but let's leave that until last.
I wanna be a eunuchs developer! Pass me a bread knife!
I assume you've checked the boot device sequence in the BIOS..? Maybe it's trying to boot over a network interface rather than from a local device. That (might?) explain the prompt for your employer's credentials. It would also explain a long delay at boot while it tries to find and/or download boot data from the network. I've never tried a network boot but googling gives plenty of experiences...
My guess would be that they re-wrote the Computer's BIOS chip. You might be able to wipe that by downloading a tool made for your motherboard by the manufacturer or possibly a 3rd party. Then you can update the BIOS chip from their site and use it to over-write the existing one.
Keep in mind, some computers use a software form of BIOS, so you first have to figure out which type. Then you will know which type of tool you need (in the event that the manufacturer can't or won't help). To get the ball rolling, get the model number and manufacturer of the computer then google those and keep the serial number written down just in case you need that too.
One other bit if advice as well as all the software stuff.
I've been reconditioning dell's for years and one thing I've always found is they misbehave strangely when clogged up with dust and crap.
Get a can of compressed air and give the fans/vents a quick blast, or if you can get in at the motherboard give the whole lot a blast with the air cannon.
Most dell's that I've come across over the year's are custom built and have all sorts of weird ass sensors in them that you don't normally find on generic pc's, when they get even a little bit of dust on some of them they frequently go stupid.
So I wrote a wrapper for The Movie DB (tmdb.org) so you can easily and efficiently query for tv show and movie data. It wraps pretty much the entire, very mature REST/json API as an object model so it's enormous.
Anyway, the neat thing about it is how it caches.
The entire object model backs its state on a normalized graph that maps directly to JSON.
it queries tmdb.org as necessary to fill in the bits of the graph it doesn't already have.
so it keeps the entire cache as one large (normalized) "JSON" object graph.
The normalization just means parsing the json into (null),string,bool, int,long,bigint, double, IList<object> and IDictionary<string,object> types and then nesting those to make the graphs.
I say graphs because the way the cache works, everything is connected, and you might have a node connected by more than one "parent" so that data isn't so duplicated.
Anyway, that caching and state backing thing could use its own article.
But it's a technique, not a separate code library.
Should I publish a Tip & Trick entry with just the caching aspect of the TmdbApi explored, or do you have better ideas?
Object graph: Simply objects nested inside objects using dictionaries and lists.
(Apparently graph databases are a thing. I did not know that.)
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
I think most people here don't even have a clue what a graph database is and probably think it has to do with graphics, so it would be a good thing to explain that first
Here some Graph databases are mentioned: best-graph-databases-suited-for-big-data[^]