Re: Simples...
the Open/Create/Replace file operation failed.
Read that as Replace File Operator Failed.
5951 publicly visible posts • joined 8 Oct 2009
It's hard to visualise how far 19 billion km is
Some 480000 times the circumference of the Earth at the equator. Going around 13 times _a day_ it would take you 100 years to cover those 19 billion km.
Or a speed of 15 km/sec meaning I could get to my office in under 3 seconds.
At that speed I don't think you'll be Gatso-ed, at least not with your license plate sufficiently unblurry, but you do have to start braking in time so as to not smash in to the wall at the far end of the parking lot.
The capacitor bank for this behemoth as about 1/2 Farad at 35 volts or so
About 200J.
I still have the capacitor bank for one of the motors from a scrapped open reel tape drive: two capacitors the size of a 1l beer tin, 68mF 50V each, with two copper bars bolted on top. 150J if you drive those caps up to their working voltage, which today may well result in a mahoosive bang if they even care to store anywhere near their rated capacity in the first place.
I vaguely recall one particular line printer model that used a loop of paper tape (probably mylar, more robust) that went with the character set on the drum. No further details; printers tended to be serviced by specialists, although just swapping a board was usually done by anyone available and I've even done the occasional hammer flight time adjustments.
Back then, "fixed in software" was much less common than "fixed in hardware". When I started at DEC, plopping in a new set of EPROMS was already the way the majority of fixes were done, but I still had to do my share of soldering and changing wire-wraps.
At one point in Uni I got hold of a HP drum printer that had character rings on its drum only every third position. To get all character positions on a line printed the paper was shuffled left and right using a hefty rocker arrangement on the paper feed mechanism. Oh, and the data buffer was built around seven bucket memory ICs[0], the rest of the electronics were simple TTL or DTL logic and discrete components. And probably a PROM for the character map, can't remember.
[0] you clock in one bit, and umpteen clock ticks later that bit appears on the output. No addressing, all you can do is count clock ticks and wait for the bit you want to turn up. Somewhat more elegant than mercury delay lines, but not that much.
In theory ammonium nitrate is an oxidizing agent and not an explosive in its own right, although very large quantities (many tons) can detonate.
As the residents of Beirut found out one sunny afternoon not too long ago.
A fairly similar chemical, ammonium perchlorate, caused Pepcon to go boom; in both cases the stuff did not ignite by itself but by a minor fire nearby.
As the desired character for a column passes correct position a hammer strikes the paper against the ink ribbon and the typeface from behind to imprint the letter.
And when you know the character arrangement on each of the positions you can send lines to be printed that make all hammers fire at once. Few printers manage to withstand that for more than a couple of minutes, although usually it's just a fuse that goes. Impressive banging while it lasts.
Same with band and chain printers, although their racket tends to be just loud, not extremely loud. Chain printers run the risk of the chain breaking under such a test; the relative advantage of a band printer is that while the band has much less mass it's a thin strip of stainless steel going at quite high speeds: and the sharp ends of a break are quite nasty to printer innards and printer technician's fingers.
"Clog Blast", since that sounds superficially amusing. But what should it be about? [1]
Exploding clogs, of course. In the same vein as Will It Blend and Hydraulic Press; you don't have to actually have something to say, just showing things going boom will get you visitors.
One fine day Facilities saw fit to upgrade the door to our computer room with a code lock but didn't upgrade our knowledge with the required code, as we weren't supposed to enter that room (we were).
No matter, the door opened outwards, and this was one of those mechanical code locks where the door knob only engages the latch bolt after entering the 4-digit code. So opening the door would only require flipping the bolt, and the hook on the serrated knife of a Leatherman Charge does that job perfectly.
What no telephone sanitary engineers?
They're on a long trip in interstellar space, as are a number of public relations managers and management consultants.
Unfortunately however, there are still quite a lot down here, waiting for the B Ark Mark 2 with its greatly enhanced carrying capacity.
Sometimes you can. Like when a garbage garbage collector doesn't do the collection, and you just have to watch the memory usage numbers, extrapolate the trend and sit back.
Maybe not to the minute, but surely "this afternoon".
The safest robots are locked into a cage just a bit bigger than their operating envelope
I would like to see this extended to these cars with their so-called Autopilot features. Only disengage the garage door lock when Autopilot has been disabled.
and nobody and nothing is ever allowed inside so long as the robot is energized.
Or that. Refuse to open the car doors to let the driver and the passengers in.
Tangentially mentioned in this Grauniad article is an opinion on blockchain transactions:
"Jason Deane, chief bitcoin analyst at Quantum Economics, said he believed there were a host of advantages, including the offer of instant, virtually free, financial transactions carried out without the use of a third party, with certainty that there will be instant settlement, and that the current teething problems need to be put in perspective."
Instant? Maye if you compare those tens of minutes for a single transaction to handing over cash in person, but otherwise it doesn't mesh. If either or both parties are using public wallets there _are_ third parties involved, the "virtually free" is again an externality where others are verifying the blockchain, and those "teething problems" are actually matters that stem from the design, not from the implementation.
I don’t see any reason why it has to be a blockchain rather than a regular database.
Regular databases tend to be controlled by a single entity, who then has to be trusted by all participants. Sure, there are methods that can build that chain of trust (where participants only have to trust their immediate 'neighbors'), but then you're already part way into a blockchain-like system. Plus, a single controlling entity can make entries disappear if they want to.
But indeed, what method you use to track a load of coffee beans or a side of beef is irrelevant if you can't verify whether that database entry or that blockchain is the one for the physical item you're looking at.
In that respect, with NFTs and cryptocurrencies the blockchain entry itself is the item of value, and thus can't be separated from it.
That would be if he'd be referring to the median. But what's commonly referred to as the average is the mean, and if you have 19 people with an IQ of 101 and one Farcebook user of 81, the average is 100 but there's just one below average, not half.
Although with large sample sizes with a Gaussian distribution mean and median tend to be close.
Kudos for whoever took care of that.
The fall of the previous cabinet (on an entirely different matter, and before this became public), the ensuing elections and uncommonly lengthy negotiations on forming a new coalition.
So, more or less democratic process as usual.
"The use of such shell companies was undoubtedly used to conceal Amazon's involvement in the planning procedure, and there could be various reasons for this. There may have been fears that the planning application might prompt an adverse reaction from those living in the area, or perhaps even have led to inflated costs if it were known that a global giant such as Amazon was involved."
Same is currently happening here in the Netherlands, FacebookMeta intends to build a datacentre near Zeewolde, Southern Flevoland, but that it are them that are behind that plan was unknown until someone involved in a tangential matter blabbed that it was FaceMeta wanting to build there.
But in contrast with Amazon a datacentre, especially a dedicated one from a giant like FaceMeta, Google or Microsoft, doesn't offer much in the way of local jobs. Of course the quality of jobs at an Amazon warehouse can be debated, but the number of bods running around in it is a fair bit larger than in a DC. Nevertheless, FaceMeta got a preferential treatment from the Minister of Economic Affairs who leaned hard on Tennet, the national energy distribution system operator, to provide them with a dedicated substation and sufficient green energy. This goes against several recommendations from civil servants at the Department of Economic Affairs that this would severely hinder the CO2 reduction goals while bringing very very little economic benefit in the form of jobs, direct and indirect. For the time being the municipal council of Zeewolde has given the green light, but this affair has triggered action to suspend that until national guidelines are in place, especially concerning area/location and energy use, and the Eerste Kamer (Upper Chamber of Parliament) has spoken against the plan. There's also the snag that half the area on which it is planned falls under the Rijksvastgoedbedrijf, the government department owning real estate, which had already put a stop on sale of agricultural area.
So, the last word hasn't been said about this matter, And in the meantime there's now a new Minister for Economic Affaiirs.
The one thing that pleases me about the choice for that particular location is that it's below sea level.
I've got a SmartEVSE[0] charger installed. Uses a PIC 18F26K22.
[0] Its smarts are limited to sensing the mains current on the incoming feed and keeping that below the current rating for the primary fuses, so that they don't blow if the cooker hobs and the oven and the electrical boiler and the kettle and a few Magicoals are running, and then you get home plugging in the EV.
There are, as can be imagined, quite a few requests to support older and abandoned kit, but to satisfy such requests one needs coders familiar with that kit as well as having access[0] to those particular models. And having the time to work on porting.
Currently, there's quite the gap there.
[0] over the Christmas/New Year holiday a coder in Pakistan was working on porting Halium to the OnePlus 1, which for the moment looks to be left behind when that upgrade gets rolled out. The phone itself was here.