(superseeded) Linuxcnc on Linux Mint 19.3 quick and easy installation

Geesh on that old of a machine I'd stick to Wheezy or something with a lighter weight desktop environment.

(So you didn't give my iso a go ? )

Yes I did . LinuxMint_19.2_Linuxcnc_2.9 would not boot up .......
I could not find a way to install_RTAI_LinuxCNC2.8 to HD -- maybe just Me over looking something . I am new and trying diff things to learn on how to use them .

My next step is to make a iso of this work LinuxmintCNC 19.3 HD (backup for say ) .

What would be the files I need for the RTAI kernel ?

WhyMe1 wrote: (So you didn't give my iso a go ? )

Yes I did . LinuxMint_19.2_Linuxcnc_2.9 would not boot up .......
I could not find a way to install_RTAI_LinuxCNC2.8 to HD -- maybe just Me over looking something . I am new and trying diff things to learn on how to use them .

My next step is to make a iso of this work LinuxmintCNC 19.3 HD (backup for say ) .

[strike]I had a look at an original Linux Mint iso and my remastered one, and there is a difference between the extension on the initrd.

Did you try using Win32DiskImager ?[/strike]

Win32DiskImager Yes - Only issues was to re-flash it -- Win10 would not see it . Had to use two diff programs to reformat so Win 10 could see it again .

[strike]Ok when you flash a usb stick with a hybrid image in windows, windows can't read the usb stick and thinks that it is not formatted. Do not worry the USB is bootable, I just tried win32diskimager myself (had to boot into windows ) and booted into Linux Mint, which I am currently using to type this message.

Etcher, Rufus and it would appear the utility you used do not do a raw byte by byte write to the USB stick. They attempt to create a bootable USB stick, format the disk and copy the files to the stick. This is not the behaviour wanted.

This issue, not being able to read a USB stick after using win32diskimager for a Hybrid iso has been discussed before. There is nothing wrong with the written image, it's just the IS can not read the particular disk format the disk has.

Even under Linux the same USB stick needs to be mount manually and when mounted if you look through run dmesg you'll see the file system used to mount it is ISO9660.[/strike]

I think the problem here is that Win10 has removed partitioning software from its distribution so you can't just revert to a single clean unformatted partition that any OS can format. So once you make a bootable disk you are kinda stuck with no return path unless you get sneaky. Bring back fdisk I say!

Yes-- that the reason why I was trying to use a diff program to flash the USB stick so I would only end up using one program to flash and re-flash it with diff OS versions.

[strike]Not quite rod, it's hidden in the disk management part of windows.

www.hdd-tool.com/windows-10/how-to-resize-partition.html

Or you can use gpated to resize disk partitions.

The problem with the fancy utils such as Old Mate used is that they are looking for initrd.lz in the image (the image is actually mounted and files copied rather than raw bytes written) where as this particular instance the initrd is named initrd.gz, hence it fails.[/strike]

fdisk --- >How about Win 10 Command prompt then DiskPart -- can that work ?