|
This message has been flagged as potential spam and is awaiting moderation
|
|
|
|
|
|
Why would you need CPU memory to read the disk drive?
From looking at their web page, their drives are all SSDs. Open the device, look at the SSD model, and then google the SSD model to see the interface type. Get an SSD enclosure that matches the SSD interface (SATA/M.2-SATA/M.2-NVMe to USB), and connect that to another PC.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Are you sure that your files are saved in processor memory? I would expect them to be on a rotating or solid state disk.
|
|
|
|
|
Your memory module is a Dynamic random-access memory[^] (the second 'D' in DD4). This type of memory doesn't retain anything the moment power goes down.
As others have said, look for somewhere else where your data is stored.
Mircea
|
|
|
|
|
I have a BeeLink also and yeah they are throw aways.
Open the case up and in the bottom is an SSD.
If you can't put it in your computer you can get one of these SSD-to-USB adapters[^] to retrieve the data.
Definition of a burocrate; Delegate, Take Credit, shift blame.
PartsBin an Electronics Part Organizer - Release Version 1.3.1 JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
Wordle 1,033 5/6
⬜⬜🟨⬜🟩
⬜🟩⬜⬜🟩
⬜🟩⬜⬜🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 1,033 3/6
⬜⬜⬜🟨🟩
🟩🟨⬜⬜🟩
🟩🟩🟩🟩🟩
Lucky second guess.
|
|
|
|
|
(17. April 2024) 4/6
⬛⬛⬛🟨⬛
⬛🟨⬛⬛⬛
⬛🟩🟩⬛⬛
🟩🟩🟩🟩🟩
Rules for the FOSW ![ ^]
MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");
|
|
|
|
|
Wordle 1,033 4/6*
⬜⬜⬜⬜🟩
⬜⬜🟩🟨🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
⬜⬜⬜⬜🟩
⬜🟩⬜⬜⬜
🟩🟩🟩⬜🟩
🟩🟩🟩🟩🟩
In a closed society where everybody's guilty, the only crime is getting caught. In a world of thieves, the only final sin is stupidity. - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 1,033 6/6
⬜⬜🟨⬜⬜
⬜🟨🟨⬜⬜
⬜⬜⬜⬜⬜
⬜🟨⬜🟨⬜
⬜🟩⬜🟨⬜
🟩🟩🟩🟩🟩
Looked it up, never would've guessed this
|
|
|
|
|
A strange one indeed!
Ok, I have had my coffee, so you can all come out now!
|
|
|
|
|
Wordle 1,033 6/6
⬛⬛⬛⬛🟩
⬛⬛🟨⬛🟩
⬛🟩⬛🟩🟩
⬛🟩🟩🟩🟩
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
Ok, I have had my coffee, so you can all come out now!
|
|
|
|
|
This application is beyond cool. It has a high learning curve, and the website needs some lovin'. But, this bad boy has made it so much more easy (relatively speaking) to automate the generation of charts from raw data when doing market analyses, rather than using Excel over and over.
gnuplot homepage
Edit: Some demos if you're so inclined.
Jeremy Falcon
modified 14hrs ago.
|
|
|
|
|
I'm very peculiar about the keyboard and mouse I'm using. Especially for my daily driver.
I'll tolerate anyone's mouse when I have to use their system, and I'll adapt to different keyboards given enough time, but I'm particularly finicky about my mouse. I still think the best mouse I've ever used was Microsoft's old IntelliMouse (their very first laser one, without a ball). Sadly at one point Microsoft stopped making them, and I spent years replacing mice after that, trying to find the ideal one, because I knew the mouse I was using wasn't going to last forever.
Then years later Microsoft revived it as the "Classic IntelliMouse". Tried one - and despite the change in color (and some white LED they somehow felt was necessary to have), it felt and performed the same. So I bought 5. Given the last one I had been using was still functional, I figured 5 would outlast me.
That wasn't all that long ago.
This morning I've opened the box for the last of those 5. What happened to quality control, MS?
The 4 others all developed problems that became severe enough I just moved onto the next one in the pile. Either the right or left buttons became too sensitive (or I had to hammer them hard). Or the on-screen pointer started moving erratically, even though I wasn't even touching the mouse. This time it was the scrollwheel - move down one 'click', it moved up by 3 and then back down by 1. The faster I tried to scroll down, the faster it scrolled up. That sort of thing. Rather infuriating.
After having put up with this for months, this one feels like bliss again. But how long will it last? I checked on Amazon, and it's either discontinued (once again), or people want hundreds of dollars for them.
No, I don't have a question. I'm not even asking for alternatives. "What happened to quality control" was rhetorical. I know what happened. I'm just commiserating.
|
|
|
|
|
Like everything else, built to fail.
I think sales people invented the concept.
Definition of a burocrate; Delegate, Take Credit, shift blame.
PartsBin an Electronics Part Organizer - Release Version 1.3.1 JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
If the warranty worked off of the "first use" date rather than purchase date, I probably could've returned them all for replacements. That's how quickly they all failed.
|
|
|
|
|
Sales team was/is really motivated?
Definition of a burocrate; Delegate, Take Credit, shift blame.
PartsBin an Electronics Part Organizer - Release Version 1.3.1 JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
When is the last time you've seen a doctor?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Hi,
I have written a bit of Code to talk to bit of hardware. All good I now having to document it for the records,
In the past I have worked on embedded and analogue test rigs which can be covered by a flowchart and a listing.
This will not work for a Windows program there is too much going on compared to a PIC or Atmel. Is there a way of creating the asked for without going mad? It can't be too odd as I think there must be other companies who need this...
|
|
|
|
|
Welcome to a reason I don't do desktop and server development anymore.
The truth is I've only ever done flow diagrams for embedded code.
To verify desktop applications, rather than design a flow diagram, I design a test matrix. My functional requirements basically dictate the tests.
If you really must diagram your software's behavior, you could use UML, but it won't make things easier, just more comprehensible because anyone with a UML background could understand it.
UML - Behavioral Diagram vs Structural Diagram[^]
Adding: To my mind this is the difference between programming realtime systems and programming non-realtime systems - realtime systems are predictable enough to diagram. As a rough rule of thumb anyway.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Well, there's the high level stuff:
1. What does the hardware do, and why?
2. What are the requirements for the code?
Mid-level stuff:
1. How to integrate the code into a project
2. How to test the code and hardware
Low-level stuff:
1. What are the "public" methods to initialize the code & hardware
2. What are the "public" methods to interact with the hardware -- read/write/reset/diagnostics, etc
3. What is a typical use-case scenario
4. What are the best practices for initialization and shutdown of the code/hardware?
5. What parts of the code are thread-safe, what parts are not? (I would assume none of it is thread safe, but who knows.)
Nano-level stuff:
1. Describe the low-level interface between the code and the hardware.
2. Describe signals and timing (or include the specs on the hardware)
3. Describe specific constraints on the code, like, are there timing dependencies
4. Describe interrupts the code uses when interacting with the hardware
My 2c of some ideas, dredging up memories of documentation I've written in the past for software-hardware stuff
|
|
|
|
|
Can a part of the documentation be written within the code itself, aka, self documenting code. In the form of class headers, function headers, etc.
And the remaining part of documentation as a high level document giving the overall architecture, hardware interfaces, assumptions, limitations, errors, etc.
|
|
|
|
|
Mmm, self documenting code, sounds good until you have to figure out how and why!
|
|
|
|