|
I hope they installed it on hump day!
Hogan
|
|
|
|
|
I had a friend whose car horn magically honked anytime he went over a speed bump
|
|
|
|
|
The car probably screamed in agony when it negotiated the bump. 
Get me coffee and no one gets hurt!
|
|
|
|
|
I try to buy DDR4 3200 RAM for my laptop(Acer Aspire 5), I searched on amazon and find two links:
1. DDR4 3200 SDRAM
2. DDR4 SO-DIMM
what are the difference for SDRAM vs. SO-DIMM? Are they both fit my Laptop? MY CPU is: Intel CPU i7 11th 1165G7.
diligent hands rule....
|
|
|
|
|
According to WikiPedia:
Quote: A SO-DIMM is a smaller alternative to a DIMM, being roughly half the physical size of a regular DIMM.
SO-DIMM - Wikipedia[^]
|
|
|
|
|
is it the same size of SDRAM?
diligent hands rule....
|
|
|
|
|
SDRAM is a type of memory, which can be SODIMM too.
|
|
|
|
|
The RAM type that is most used in laptops is SO-DIMM. I am not sure of the technical differences, other than that they have different form factors, and differing numbers of leads. They are not compatible with each other!
I assume that you have checked that the memory's clock parameters are compatible with your laptop. This data may be found in the memory manufacturer's datasheet, which you can usually find online. A freeware program, CPU-Z, may be used to check the clock parameters of your laptop's memory, along with all manner of other interesting data.
Most laptops have either one or two slots for memory.
If you have a two-slot model, you should buy the same type of memory (manufacturer, size) for the second slot that is present in the first slot of your laptop. This will allow the laptop to use the memory in dual configuration, which can be faster. If you are replacing the memory in both slots, use memory from the same manufacturer. If has likely been tested by the manufacturer of your laptop, so is less likely to cause problems.
If you have a single-slot model, I would recommend getting memory from the same manufacturer for the reason given above.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
|
Daniel Pfeffer wrote: They are not compatible with each other!
Actually they are electrically and protocol compatible but are not physically compatible because SO-DIMMs (laptop memory) are smaller than DIMM (desktop memory). If you search, there are pass-through adapters to connect SO-DIMMs to DIMM slots (but not the other way around since DIMMs would never fit inside a laptop).
The difference in pins is due to DIMMs having many "NC" ("Not connected") and reserved pins. Maybe for planned features that were never implemented (maybe more address pins for bigger memories but was scraped because they would be too expensive and no one would buy them?).
Daniel Pfeffer wrote: If you have a two-slot model, you should buy the same type of memory (manufacturer, size) for the second slot that is present in the first slot of your laptop
Even though just adding a second SO-DIMM module with the same characteristics from the same manufacturer usually works (I have done this successfully), the recommendation is to buy a pair of SO-DIMMs and replace all memory.
Because slight differences in timings in modules produced at different times can lead to read/write errors which can translate into slow memory (due to retries or memory page faults) or worse, random reboots of the computer (which also happened to me before because I didn't follow the recommendation).
Memory sold in pairs (or in fours) is tested together and has a manufacturer warranty that they read/write exactly at the same time within the specifications.
For all interested:
* SRAM, DRAM, SIMM, DIMM, RIMM, etc define RAM architecture
* EDO (DRAM), SDR(SIMM, DIMM), DDRx (SIMM, DIMM), etc define the communication protocol and electrical connections which is also dependent on architecture
* SO(SIMM, DIMM), etc define the packaging
@Southmountain, as others said, you should check your laptop manufacturer for compatible memory and preferably buy memory that is on their compatibility list for assured stability. If you want something that is not on their list try to match the timings with something that is on their list. Example: you want memory with timings 7-7-7-21 but the fastest memory on the compatibility list is 8-8-8-24 then you should not buy that one and go for one that is 8-8-8-24 or slower. If you buy just one module to add to an existing one, put your system with both modules through a stress test to make sure that, if it fails, it will likely fail during the test (and not during some important work) and early enough for you to return it. Otherwise, because memories are so fast, errors may occur without you even being aware of until it fails catastrophically (laptop random reboot or programs crashing).
|
|
|
|
|
I highly appreciate your input. will follow your suggestions.
diligent hands rule....
|
|
|
|
|
|
I did some research on google, but still feel my question not answered, so I post here to seek you guys' input.
diligent hands rule....
|
|
|
|
|
it's a laptop - SO-DIMM. Issue solved. The other poster is correct - motherboard connectors for RAM are much larger. I have never seen a motherboard use SO-DIMM.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
thank you All!
I find a link from Crucial to scan my Laptop to find the right RAM.
diligent hands rule....
|
|
|
|
|
I was going to suggest this. Glad you found it. 
|
|
|
|
|
I take the lazy route and run a Crucial scan which then shows me which ram is compatible.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
|
thanks for the link. I take note of it.
diligent hands rule....
|
|
|
|
|
At least one or more of the companies that manufacture/sell memory have an app on their website that can scan your computer and tell you exactly what kind of memory to get.
Scott
|
|
|
|
|
SO-DIMMs are roughly half the length of full sized DIMMs and are normally used in laptops and small form factor systems, full sized DIMMs are used in desktops and servers.
Both linked memory modules are SO-DIMMs. The first one lists the size partway down the page under "RAM Memory Technology: DDR4, SO-DIMM".
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
thanks for clarification!
I am not strong on hardware side although I have theoretical background.
after post this question in the lounge, I got confidence in my understanding on this question from you guys.
diligent hands rule....
|
|
|
|
|
...all I want to do is create a base class form, and derive a bunch of others from it - the idea being to have a base which has the "general layout" and a bunch of buttons that will be on all forms.
And the first problem is that you can't use a static ImageList for all the buttons.
And an Imagelist is the only way to use my .ICO file as button images.
After going round that for a while (including a perfect looking article here: Sharing and inheriting ImageLists across multiple forms and controls[^] which sounds perfect but doesn't work with VS2019 and I'd had enough of trying by then) I relent and find an online resource that extracts PNG images form Icons.
Except they are all too big at 256x256 and the ICO files don't have the right 64x64 images, just 256x256 and 48x48 and smaller. 
OK ... Corel Paintshop Pro has a batch mode ... finally get that working, import the PNG files, apply, presto! Base form is working.
Derive a new form. try to view it in the designer ... "Object reference not set to an instance". Find the reason, add the necessary "if design mode", try again.
"System.Windows.Forms.Design.IEventHandlerService already exists in the service container. Parameter name: serviceType" 
Finally fix it: change the derived form type to "Form", build, view in the designer. Hurrah! No error (or buttons but hey!). Change it back to Base Form. Build. View in the designer.
And it works.
Sodding Visual Studio.
And it's only Tuesday. I am sooooo glad I didn't make the base form abstract ... I'll do that when its' all working. Deriving a concrete class from an abstract UserControl[^] applies to Forms as well.
"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!
|
|
|
|
|
|
Not meaning to pick nits, but doesn't 'going round and round' imply circles  
Thar's only two possibilities: Thar is life out there in the universe which is smarter than we are, or we're the most intelligent life in the universe. Either way, it's a mighty sobering thought. (Porkypine - via Walt Kelly)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://codeproject.freetls.fastly.net/script/Forums/Images/rose.gif)
![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)