fordy_rounds

I mean, you saw my screenshot, right? I have my "server" folding at just over 1300 PPD. In case you didn't see it, here's a clip:

 
Now sure, I also have my desktop (both CPU and GPU) folding at a total of 6-700K.... but that's not the point.

According to your manual (linked above) it's labeled "JFP1." See page 32 of the manual for a guide to where it's located on the board—looks to be centered on the bottom edge (below the pcie slots).

As far as I can tell. The split connectors are just for boards with non-standard headers, and yours look to be standard.

Woohoo, 79th on Day one! Last year I hovered around the 90s, so I'm happy so far.
I also added some new hardware. I don't think it's going to make much difference though....

 
It's my storage server's CPU, a 10-year-old Athlon (and a GPU that I added in for Plex transcoding, though I haven't actually used it, and it's too old to be supported by F@H) running Linux. (It's a terrible CPU, but it's also a very lightly used server, so it does what I need it to, and it was free.)

Woohoo, 79th on Day one! Last year I hovered around the 90s, so I'm happy so far.
I also added some new hardware. I don't think it's going to make much difference though....

 
It's my storage server's CPU, a 10-year-old Athlon (and a GPU that I added in for Plex transcoding, though I haven't actually used it, and it's too old to be supported by F@H) running Linux. (It's a terrible CPU, but it's also a very lightly used server, so it does what I need it to, and it was free.)

Woohoo, 79th on Day one! Last year I hovered around the 90s, so I'm happy so far.
I also added some new hardware. I don't think it's going to make much difference though....

 
It's my storage server's CPU, a 10-year-old Athlon (and a GPU that I added in for Plex transcoding, though I haven't actually used it, and it's too old to be supported by F@H) running Linux. (It's a terrible CPU, but it's also a very lightly used server, so it does what I need it to, and it was free.)

Woohoo, 79th on Day one! Last year I hovered around the 90s, so I'm happy so far.
I also added some new hardware. I don't think it's going to make much difference though....

 
It's my storage server's CPU, a 10-year-old Athlon (and a GPU that I added in for Plex transcoding, though I haven't actually used it, and it's too old to be supported by F@H) running Linux. (It's a terrible CPU, but it's also a very lightly used server, so it does what I need it to, and it was free.)

Woohoo, 79th on Day one! Last year I hovered around the 90s, so I'm happy so far.
I also added some new hardware. I don't think it's going to make much difference though....

 
It's my storage server's CPU, a 10-year-old Athlon (and a GPU that I added in for Plex transcoding, though I haven't actually used it, and it's too old to be supported by F@H) running Linux. (It's a terrible CPU, but it's also a very lightly used server, so it does what I need it to, and it was free.)

So both my computer projects have been on the backburner, no updates on the PS2 build if anyone is following that either.
 
But I've slowly been working on a new shell for the Dreamcast. I de-soldered the DVI connector on the graphics card, and along with some shroud changes that should improve airflow out of the case.
 
As you can see I'm retaining some plastic across the back so it's not a horseshoe shape like before. It's much stronger than the last one 💪🏻
 
 

 
 
Still working out how to retain the spring loaded mechanism for the lid, but that's looking unlikely.... brainstorming is ongoing! Aside from being bulky, the original one sided spring was so strong, that it made the lid sit twisted when it was closed. I'm looking at slightly weaker springs, on both sides.
 
As for the front panel buttons and led....I discovered why my reset button stopped working 😭 clearly dismantling the shell repeatedly has taken its toll. To try and reduce the risk of frayed wires, I'm going to take a rather cool approach for getting the wiring between the two halves of the shell. Magnetic contact pins, often seen on things like lithium ion batteries. They're expensive...but should allow for seamless opening and closing of the case 😎
 
 

 

googled the display p/n with "hdmi" behind it, first hit was this thing:
https://www.amazon.com/Controller-HSD101PFW2-CLAA101WB03-1024x600-40Pins/dp/B06X9BG8GD
then there's aliexpress:
https://www.aliexpress.com/item/4001166987319.html
ebay:
https://www.ebay.com/itm/361001303655

Thanks! AOMEI worked, and I can browse through the files now. 😄

Yep. Go into bios, find the setting for either XMP or DOCP (two names for basically the same thing). Should be an XMP profile for 3200 listed.

Yep. Go into bios, find the setting for either XMP or DOCP (two names for basically the same thing). Should be an XMP profile for 3200 listed.

C doesn't handle strings well, as you're finding out. Both of these functions have errors, just the first is run-time and the second is compile-time.
In the first version, you have 
char * out = malloc(0); which might work with your compiler, but won't necessarily work with any C compiler. (Some compilers return a NULL pointer for malloc(0), which means that you'll get a segmentation fault when you use this in the sprintf call.) The problem is that you're not actually allocating any space here; technically, even though your compiler returns an apparently valid pointer, any use of it (such as in sprintf) is a buffer overflow error. (If you're malloc-ing anything else, you might overwrite it and cause errors.) To fix this, figure out how many chars you'll actually need (some math from the string length will get you there) and malloc that number. (i.e., if strlen returns a two-digit number, you need 6 chars [2 for the first number, 1 for the /, 2 for the second number, and 1 for the null char at the end]; if it's three-digits you need 8, etc.)
The other issue here is that by malloc-ing a char* and returning it from the function, you're putting the burden of free-ing it onto the calling code, and if that doesn't happen, you could get a memory leak.
 
Version 2, without the malloc, doesn't work because the pointer is pointing to a read-only string literal. Thus, when you try to change it (with sprintf), there is an error. A fix here is to use the fact that arrays and pointers are closely related, and use 
char out[16]; This will most probably allocate more characters than you actually need, but that's ok, it's better to have too many than too few. (From my math above, this allows up to a 7-digit number of chars in the original string, or up to 9,999,999 characters. You could adjust the 16 to allow whatever number size you think you'll need; however, it has to be set at compile-time, and cannot by dynamic. If you want it dynamic, you have to malloc it.) This allocates the space onto the stack instead of the heap, which means that it'll automatically be freed without a memory leak.
 
On a side note, once you know how long "out" can be (whether malloc-ed or statically assigned), you should use snprintf instead of sprintf to ensure there's no buffer overflow. (Example: if I use malloc(4), then try to print "1/10", that's 5 characters, and I've overflowed the allocated space. sprintf will let you do this; snprintf takes the 4 as an argument and will only allow up to 4 chars.)
 
In summary, here's your answers:
1) Why does the pointer "out" need to be malloced?
    It doesn't have to be, but that's the only way to get a dynamic array length. If you're ok with a static length, you can use e.g. char out[10]; instead.
2) Is there a way to write this program without using malloc( ) ?
    Yes, but only with a static array length, as above.
3) If malloc is used inside the function, how can I free the pointer "out"?
    - I read you should always free any memory allocated with malloc( )
    Yes, that's correct. Since you're returning the pointer, the calling function assumes the responsibility for freeing it. This is messy, and is often the cause of memory leaks. In this case, it might look something like:
char* output = printerError(myString); // do something else with 'output' free(output);  

C doesn't handle strings well, as you're finding out. Both of these functions have errors, just the first is run-time and the second is compile-time.
In the first version, you have 
char * out = malloc(0); which might work with your compiler, but won't necessarily work with any C compiler. (Some compilers return a NULL pointer for malloc(0), which means that you'll get a segmentation fault when you use this in the sprintf call.) The problem is that you're not actually allocating any space here; technically, even though your compiler returns an apparently valid pointer, any use of it (such as in sprintf) is a buffer overflow error. (If you're malloc-ing anything else, you might overwrite it and cause errors.) To fix this, figure out how many chars you'll actually need (some math from the string length will get you there) and malloc that number. (i.e., if strlen returns a two-digit number, you need 6 chars [2 for the first number, 1 for the /, 2 for the second number, and 1 for the null char at the end]; if it's three-digits you need 8, etc.)
The other issue here is that by malloc-ing a char* and returning it from the function, you're putting the burden of free-ing it onto the calling code, and if that doesn't happen, you could get a memory leak.
 
Version 2, without the malloc, doesn't work because the pointer is pointing to a read-only string literal. Thus, when you try to change it (with sprintf), there is an error. A fix here is to use the fact that arrays and pointers are closely related, and use 
char out[16]; This will most probably allocate more characters than you actually need, but that's ok, it's better to have too many than too few. (From my math above, this allows up to a 7-digit number of chars in the original string, or up to 9,999,999 characters. You could adjust the 16 to allow whatever number size you think you'll need; however, it has to be set at compile-time, and cannot by dynamic. If you want it dynamic, you have to malloc it.) This allocates the space onto the stack instead of the heap, which means that it'll automatically be freed without a memory leak.
 
On a side note, once you know how long "out" can be (whether malloc-ed or statically assigned), you should use snprintf instead of sprintf to ensure there's no buffer overflow. (Example: if I use malloc(4), then try to print "1/10", that's 5 characters, and I've overflowed the allocated space. sprintf will let you do this; snprintf takes the 4 as an argument and will only allow up to 4 chars.)
 
In summary, here's your answers:
1) Why does the pointer "out" need to be malloced?
    It doesn't have to be, but that's the only way to get a dynamic array length. If you're ok with a static length, you can use e.g. char out[10]; instead.
2) Is there a way to write this program without using malloc( ) ?
    Yes, but only with a static array length, as above.
3) If malloc is used inside the function, how can I free the pointer "out"?
    - I read you should always free any memory allocated with malloc( )
    Yes, that's correct. Since you're returning the pointer, the calling function assumes the responsibility for freeing it. This is messy, and is often the cause of memory leaks. In this case, it might look something like:
char* output = printerError(myString); // do something else with 'output' free(output);  

Please, don't let one hater get you down. I loved the Dreamcast build, and I'm intently watching this one too, dreaming that someday I might do something so ambitious....

Please, don't let one hater get you down. I loved the Dreamcast build, and I'm intently watching this one too, dreaming that someday I might do something so ambitious....

Hi community,

This post is more about emotional sharing than anything else really. So I'm a psych major student, I work on the side at a fast food chain - pretty hard but the pay is good (12€/h).
I like spoiling my sister for Xmas and my mom doesn't have much money.
This year I decided to give my 14y/o sis her first very own Laptop! 
 
So I get myself an absolute deal on Facebook Marketplace: A 2019 HP Pavillion i7 10th gen, 8GB of RAM, 512gb SSD, 1080p IPS 15.6" - backlit keyboard, all sorts of IO connections for 465€! It has 1 year warranty left.
In addition, the guy includes a laptop bag and a M220 wireless mouse, pretty cool right?

Thing is, the fan goes WWOOOOOSSHHHHHH on startup and it just doesn't stop. Pretty annoying. I download CPU FAN: 55-75°C on idle: noice. 
By the way, the seller had this ABSOLUTE UNIT of a Cat. It meowed, walked and looked like the Dwayne Johnsons of cats. That cat must've been the mayor of the town's cats.
Anyway, I tell myself the reason why the fan struggles so much is that there's too many cat hair or dust in the laptop, maybe.

So I open it up: spotless. Damn. I spray around with my little airbottle compressor thingy I usually use for my keyboard. Maybe they forgot to apply thermal paste? So I unscrew the cooler and boi...
There was a litteral (but figurative) OCEAN of thermal paste; like the verge pc^10. Holy moly, no wonder the fan spins like an autistic child's fidget spinner, the heat just gets trapped into that swamp of thermal paste.
So, I take out the isopropylic alcohol, wash the damn thing and I apply that sweet MX4 at corresponding dosage. Close everything up: boom 28°C idle, silent as hell.

I was so happy, so proud. I'm stoked to see my sis' reaction to that prreeeeeemiuuuum Laptop I got her.
465€ for a one-year-old +1000€ Laptop, damn today was a good day!

Thanks for reading!

PS: That cat was so big, jesus 

Motherboards that come with wifi usually have it installed via an A/E slot (including newer laptops; older laptops used mPCIe). So this is, I think, meant more as an upgrade than as a new component. You can get x1->A/E adapters, but they usually come as WiFi adapters (i.e., with the the WiFi card already slotted in), so again, this would be an upgrade.
Honestly, it would probably be cheaper just to get an AX200 PCIe card than to get this + an adapter.

A solid portion of this is you, @Den-Fi. Nearly a billion points is a lot of progress toward killing Covid. Thanks!

A solid portion of this is you, @Den-Fi. Nearly a billion points is a lot of progress toward killing Covid. Thanks!

A solid portion of this is you, @Den-Fi. Nearly a billion points is a lot of progress toward killing Covid. Thanks!

Yes, it is. It looks like most/all of these are equality of int or char types, so they would be better implemented as switch statements. (The inequalities (that's <, <=, >, or >= ) need to be if/else's still.)
 
And a few other notes, OP: short variable names don't make your code more efficient. Help us, and yourself, with some real names (i.e. use employment_status or employmentStatus rather than es). I don't have any idea what gi, ba, ot, etc, mean, and if you set this down and come back to it in two weeks, you probably won't, either.
 
Statements like if(es=='r||R') don't work the way you want it to; in fact, it won't even compile. Use if(toUpper(es)=='R') instead (though, as above, switch(toUpper(es)) is even better).
 
Also, for user-friendliness, sentence-case your outputs so we don't feel like your program is screaming at us.
 
That's about all the help I can give without more specific questions.

Even if it didn't come with a driver CD, check the manufacturer's website to see if they need to be downloaded.

The finer details continue