Re: Oh the dreaded 11th finger...
They used to be! Now you need the motherboard manual and its either on a CD or online and the bios is beeping...
8318 publicly visible posts • joined 11 Jun 2009
I've got some coax stuff in the man shed that I think would probably still work. Largely because the coax is pure copper. I may be wrong but a lot of the stuff that came out early on seemed to be made of tinned iron - makes your average dunked biscuit look moveable.
Big thanks to David though - and a lesson for people today - the man was an engineer and learned whatever was relevant to the needs of the job at the time.
Pigs that are culled are NOT eaten. You need them slaughtered for that - that requires a vet to check the meat is edible, The vets have gone back to the EU hence the need to cull animals - pigs especially as they cost as much as tory ministers to keep alive.
I'd be inclined to believe Upton that there isn't a RISC-V SOC that is as cost effective as the ARM options. Its probably beyond expecting the Raspberry gang to be able to rapidly obtain the chip design skills to contemplate evaluating a no-yet-gone-to-silicon design. I'm fairly sure in the next couple of years there will be available parts if not a complete silicon SOC available and then perhaps they can have a look at cross-compiling Rasbian and all the apps to it and launching another revolution in credit-card sized PCs. For now they are best to stick with what works. Pi5 may be a RISK-V design but its too much to ask Upton and co to make that leap now.
I worked at what was then BTRL for 10 years. In the tech side all the managers were promoted engineers. Some of them were not the best managers by far but what I did discover is they were a lot better than managers trained as managers with no real knowledge of engineering! Overpromoted salesoinks are pretty frightening too - you may think you can persuade me but the electrons say fuck you dickhead!
Using Freedos in a VM you can easily set up a shared drive to exchange data between Freedos and Linux, and I would imagine Windows too, You may be able to print to file from Locoscript and then print that from the shared directory. I have seen software that will take old dotprinter and daisy wheel data and make new documents - including HTML so you dont have to kill trees - from it.
Given that the early software like that tended to store data in fixed length records you may find a dig around the files and counting a few characters make allow you to cut and paste the data pretty much straight into a more dependable/open app. I used to make a few beers writing little programs that fseek'ed around DB files to make reports at speeds users complained couldnt have done the jobs they wanted - the reports were correct but generating things in a second or two that took the DB system a couple of hours to run confused them. Having said that running an 8086 at several GHz can alleviate problems like that but having a good copy of old data in a modern app often has many advantages - long term access to the data being one of them.
I was lucky enough to work somewhere new toys appeared from time to time. Most of my programming work was done on Vax VMS. The PC early on has a DOS IDE (C?) which I used for a while which I remember as being very similar to RHIDE and may had helped inspire it. The PC memory models were a nightmare and the only advantage was the IDE which I used for initial development and then flipped the code over to the VAX when I needed to analyse data larger than a couple of sheets of A4 which would run fine on the VAX but frequently come up with gibberish due to 64k boundaries not being bound. I still think the 80s were a largely null point in programming development due to the 8088 choice by IBM and is the reason why IT is the niche thing it still really is when it should be embedded in almost every career and would be if the BSOD had not been the result of most people introduction to programming.
I found the Studio versions of Linux which use some realtime stuff do handle things a lot better until you play with the wrong settings. Real Time is not easy to debug (or at least I haven't worked out how to do it) when something wont let the debugger start.
Anyone know a good website/PDF on this stuff?
(not replying here the above is a imposter (appropriate cheeky icon here))*
One thing about a RT system is its easy to write code that demand attention and without considerable experience the whole thing grinds to a judder and the user experience gets kinetic.
I often wonder if the main reason RT remains the domain of embedded is because it restricts you to a head-full of code that you can actually as a human being understand and control - well a top of the range human being in many cases.
* I have wondered sometimes how I managed to write such coherent posts and then get so pissed so quickly that I forgot writing them. Then I realised the space was missing!
If you have the resources these things aren't too hard to discover if you're patient.
A honeytrap machine can be duplicated and left running exposed and monitored for any unusual traffic or at reasonable time intervals and then a cross check with the duplicate can reveal the new code.
Then the fun starts - do you report or exploit?
1) You may find you have security updates set to automatically install re:unattended-upgr?
2) You may be pointing at alternative (country based?) repositories that have not been updated as yet.
I hope its 1.
https://www.cyberciti.biz/faq/how-to-set-up-automatic-updates-for-ubuntu-linux-18-04/ may help you go full tonto on it.
I'm going to have to find the phone I rarely use to see what model it was in case someone other than google/meta are eavesdropping on my food orders that all end in 'sorry we dont deliver there' no matter how much I order.
There are some benefits of living in the sticks - especially when stormy weather saves you cutting your own sticks!
I cant find any figures out there but when I was a lad CMOS you weren't using was not a noticeable power drain, it was as good as off. Now with these sub 10nm processes I'd put money on there being leakage that could easily amount to a significant power drain unless there is no power to it. So that's going to be either some noticeable real estate wasted to isolate it or a waste of power. Either way the customer is going to end up paying for something they aren't using.
Its annoying that WASM is even necessary. Netscape (IIRC) offered a Javascript2 with proper classes and inheritance over 20 years ago. I installed it into my browser (god that was a challenge!) and wrote basically a desktop gui in a few hours with SVG on steroids. As I understand it MS and Apple stopped it becoming part of the official standard.
You can get them down easily - the trouble is they would be crushed! The pressure there is 400 times atmospheric so the lift would be around 1/400 of what it is at the surface and the balls would all pop out through holes long before you got enough in to provide the lift.