|
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 believe you're looking at a combo of what Phil and David writes about.
|
|
|
|
|
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...
|
|
|
|
|
Hmm, if you are using UEFI check whether the Secure Boot option is enabled. If it is then try disabling it. It is the only thing I can think of, so it is probably wrong 
|
|
|
|
|
Have you tried doing a UEFI reset? UEFI is waaaaay more complicated than the BIOS used to be, and remembers more stateful data than BIOSes ever did. This Dell support page might help...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
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.
modified 1-Sep-19 14:29pm.
|
|
|
|
|
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[^]
|
|
|
|
|
i didn't know a graph database was a thing as such. i'll edit my comment.
i was just talking about an object graph. but i suppose that's what a graph DB would hold.
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've used neo4j and would recommend it if you use Java. They have a really good intro article to the topic too - What is a Graph Database?[^] 
|
|
|
|
|
this one is all in C#. It's not really a full fledged DB.
It's simplistic but good for what i needed it to do.
Literally all the "indexers" are are just thinly wrapped Dictionary<string,object> instances.
Each Dictionary<string,object> is a JSON object. Each List<object> is a JSON array. The scalar values for object can be numeric, string, boolean or null, just like JSON, but they can also be more lists and dictionaries.
It all maps directly. It's so easy it's stupid, but smart enough to work.
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've heard of it, but it's overkill for this. If this was serving json rather than consuming it I'd consider it, but all i need is simple caching.
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.
|
|
|
|
|
Neo4j is quite interesting: it runs on Java. The free book is very well-written.
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot
|
|
|
|
|
honey the codewitch wrote: 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?
It sounds like it would fit better as an Article than as a Tip (unless I'm overestimating the amount you can write about it). But it doesn't matter that it's a technique instead of a code library... there's no problem whatsoever with writing an article about a technique.
|
|
|
|
|
This could become a very valuable CP article.
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot
|
|
|
|
|
I wonder how many services out there expose their APIs as JSON (content-type: application/json) over HTTP REST?
If so, I might have a dynamic, (read-only) caching entity framework for querying such a monster.
All of the really cool stuff though - like the automatic paging is very service specific regardless.
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.
|
|
|
|
|
|
For a new vernier caliper - the cat has damaged mine - and I'm in two minds if I want a new-fangled digital, or stick with the traditional "true" vernier.
I find a good 'un:
Material: Carbon Steel Excellent!
Measuring range: 150mm Perfect
Measurement accuracy: 0.02mm I'd prefer .01mm, but 2 / 100ths is fine.
Note:
Please allow 0-2cm error due to manual measurement. Thanks for your understanding. Hang on, hang on. You sell vernier calipers - the accurate way to measure things - and you can't get a closer tolerance than 0-2cm? 
What are they teaching the Youth of Today? 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: What are they teaching the Youth of Today?
Probably the same stuff as our QA students get to learn. The recent question from a "teacher" was a case in point.
|
|
|
|
|
Just legal-speak I'm sure.
|
|
|
|
|
As in "use of this tool can result in finger blisters, broken nails, myopia, and, possibly, death"?
It seems to work OK for the drug companies, so you're probably right.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
