Welcome to the Lounge

Ron Anders1-Jan-20 16:40

Ron Anders

1-Jan-20 16:40

Nice job.

Carbon Copy Cloner is what we use too. Thumbs Up | :thumbsup:

raddevus1-Jan-20 16:48

raddevus

1-Jan-20 16:48

Ron Anders wrote:
Nice job.

Thanks, there were a couple of tricky parts. Luckily my son had a #6 Torx Security driver.
I had a #6 torx (star driver) but it wasn't the "Security" type with the hole in the middle. That is really ridiculous!

Also, check the Step 23 (in the ifixit guide[^]). You need a special wire tool to stick in those two holes so you can pry the mainboard out of the case. It is really ridiculous.
I didn't notice I needed a special tool until I got to that step and the thing was already torn apart.
I walked around the house trying to find something with wire that was the correct size that I could use and finally found a spring on an old chip clip. I cut the thing with some tin snips and somehow got it to work. That step is another ridiculous part of the tear down.

foggles2-Jan-20 1:39

foggles

2-Jan-20 1:39

At first, I couldn't even get the the mac to recognize and mount the SSD so I could clone, but I finally got that working.

How did you get this working? I got hung up here doing an iFixit SSD upgrade to my macbook pro and decided to pass on the upgrade.

raddevus2-Jan-20 4:06

raddevus

2-Jan-20 4:06

foggles wrote:
How did you get this working?

Here are the steps I took...
1) attached my Amazon.com: Inateck USB 3.0 Hard Drives Docking Station for 2.5 Inch and 3.5 Inch HDD SSD SATA I/II/III, Support UASP and 10TB Drives, Optimized for Ssd(Fd1003): Computers & Accessories[^] to the Mac Mini USB port. (I had this device from previous windows-based HDDs that I've cloned to SSDs.)

2) inserted the new SanDisk 250GB SSD
3) The disk wasn't readily recognized and I had to look around to find out how to do that-- finally found the disk utility and I had to erase and reformat the SSD - https://support.apple.com/guide/disk-utility/erase-and-reformat-a-storage-device-dskutl14079/19.0/mac/10.15[^]

After that, I could see the drive was attached, but I tried the EaseUS software and it said it could not create a bootable clone.

4) searched for and found the Copy Cloner software and it did the rest. Pick your source and your target) and Copy Cloner takes care of it.

5) I was quite nervous after taking the entire thing apart and re-assembling because there was no way to know for sure that Copy Cloner had gotten everything correct, but the computer booted up perfectly from the cloned SSD.

That's it.

It's probably that first thing that you need -- the Mac Disk Utility.
Good luck. Thumbs Up | :thumbsup:

foggles2-Jan-20 18:21

foggles

2-Jan-20 18:21

Thanks for the info. The kit I bought (OWC 1.0TB Aura Pro X2) had an enclosure but the enclosure only supported the old (current) drive and not the new one. I had put the new ssd in the machine and attempted to set it up using disk utility in recovery mode (or whatever that mode is) but it wouldn't recognize the new drive. After a few attempts I decided to return the drive and put the return funds toward an eventual new machine as I'm coming up on 7 years with the laptop.
Enjoy your spruced up machine!

Stuart Dootson6-Jan-20 23:58

Stuart Dootson

6-Jan-20 23:58

If you mean after it's been formatted with APFS or HFS+, it could be you need to use the Startup Manager to tell macOS about the new startup disk... I remember having to do that when adding an SSD boot drive to my MacBook Pro back in 2010. Start booting, but press the Option key as you turn on the power and keep it pressed to get to the Startup Manager.

Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

foggles7-Jan-20 6:49

foggles

7-Jan-20 6:49

No, I didn't make it that far. It was as if it wasn't there at all as far as Disk Utility was concerned.

dandy722-Jan-20 2:52

dandy72

2-Jan-20 2:52

Well, I know it's not the same device at all, but I've now discounted the possibility of me ever taking the time to replace the drive in my (even older) MacBook Pro.

I've been building my own PCs since I was a teenager, but I lack the finesse to take laptops apart...much less Apple ones.

raddevus2-Jan-20 4:11

raddevus

2-Jan-20 4:11

dandy72 wrote:
I've been building my own PCs since I was a teenager, but I lack the finesse to take laptops apart...much less Apple ones.

My first job was building PCs back when Windows 3.0 and 386 chips were hot.
Yeah, I feel the same way about taking laptops apart.
A couple of years ago I bought my wife a brand new laptop and it had an HDD and Win10 started updating and it was terribly slow. I (nervously) took it apart the first night we owned it and replaced the HDD with her older SSD. Instant speed! SSDs are the modern panacea for what ails you. Laugh | :laugh:

Anyways, we had older toshiba laptops (win7 2010 or so) which had nice little doors on back so you could replace or upgrade HDDs and RAM. Now all the laptops are one smooth piece that are tricky to remove and replace.

dandy723-Jan-20 3:31

dandy72

3-Jan-20 3:31

raddevus wrote:
nice little doors on back so you could replace or upgrade HDDs and RAM. Now all the laptops are one smooth piece that are tricky to remove and replace.

Exactly. I've only ever bought a single brand new laptop in my entire life - everything else was "previously enjoyed". I have a bunch of spare 2.5" drives that I swap around to try out Linux distributions that don't like virtualization all that much. If I can't swap out the drive in less than 2 minutes, I want nothing to do with that laptop.

Ouch. I want to get out and push

matblue253-Jan-20 9:31

matblue25

3-Jan-20 9:31

I’ve done the same for several older Windows laptops. Makes a huge difference going from a 5400 rpm HDD to an SSD. Like a whole new machine. They were much simpler than what you describe doing. Not sure I would have even attempted it in a Mac. Seems like Apple doesn’t like people fooling around inside their boxes.

honey the codewitch1-Jan-20 5:12

1-Jan-20 5:12

Parsley parses pretty slowly compared to a table driven parser.

It kind of makes me wonder about C# microsoft's parser, which is fast but i heard was also recursive descent.

I need to profile this mess.

When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.

User 110609791-Jan-20 5:37

1-Jan-20 5:37

Quote:
It kind of makes me wonder about C# microsoft's parser, which is fast but i heard was also recursive descent.

What I heard/read, Microsoft worked several more days on it with several dozen programmers. Therefore no need to feel bad for your work Wink | ;)

It does not solve my Problem, but it answers my question

modified 19-Jan-21 21:04pm.

honey the codewitch1-Jan-20 5:43

1-Jan-20 5:43

I mean, it's not so much feeling bad, but knowing I can improve it, seeing as how i think my hand written parser is faster right now too thought it really should be *at least* as slow.

Or maybe i'm just expecting too much of it. Unlike PCK it can't stream - because it's recursive descent!, so it has to parse the entire stream into memory before you can have it.

The lag time sucks for large documents. With PCK i was never sure how "fast" it was, because it would start spitting nodes at me instantaneously - it streamed - it was a pull parser generator so it made parsers like Microsoft's XmlReader interface. When building the tree there was lag though, but it was a separate process in PCK. In Parsley it's integrated to the parse. Hard to profile each individually but not impossible.

Unfortunately, I can't generate FIRSTS(k) and FOLLOWS(k) sets for k>1 - I just don't know how and can't figure it out though i read a research paper that gave me an idea, i have yet to try it.

Then *maybe* with a table driven parser i could parse C#, but so far what i've seen of antlr, it can't do it.

When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.

Greg Utas1-Jan-20 6:29

Greg Utas

1-Jan-20 6:29

In some code that you posted, it looked like you were using exceptions a lot, maybe even for backtracking. This would be deadly, especially it backtracks a fair bit.

honey the codewitch1-Jan-20 6:31

1-Jan-20 6:31

It doesn't backtrack except when it has to. And in .NET exceptions aren't the perf killer they are in C++.

I could do it without exceptions but it would double the code size as I add TryParse to everything.

When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.

User 110609791-Jan-20 6:48

1-Jan-20 6:48

Most probably I'm lost in all this parsing stuff...

Quote:
it would double the code size as I add TryParse to everything

It is generated code, so who cares?

It does not solve my Problem, but it answers my question

modified 19-Jan-21 21:04pm.

honey the codewitch1-Jan-20 6:50

1-Jan-20 6:50

Visual studio is starting to choke on it. It wasn't giving me proper line #'s for compile errors in the generated code last night.

The source file is 1.3MB

So... I don't want it to be 2.5 or so.

When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.

User 110609791-Jan-20 7:04

1-Jan-20 7:04

zip it

It does not solve my Problem, but it answers my question

modified 19-Jan-21 21:04pm.

honey the codewitch1-Jan-20 11:29

1-Jan-20 11:29

I can minify it. Shave a few KB at least.

Laugh | :laugh:

When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.

User 110609794-Jan-20 3:31

4-Jan-20 3:31

Probably a naive question: Would UTF8 be counterproductive?

It does not solve my Problem, but it answers my question

modified 19-Jan-21 21:04pm.

honey the codewitch4-Jan-20 3:36

4-Jan-20 3:36

i think it already is

When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.

Greg Utas1-Jan-20 6:57

Greg Utas

1-Jan-20 6:57

0x01AA said:
What I heard/read, Microsoft worked several more days on it with several dozen programmers.

I was going to make a catty remark about too many cooks but then realized that a recursive descent parser should actually lend itself well to this kind of parallel development.

User 110609791-Jan-20 7:46