Amended: Repetier Host a 3D printer program created the registry material...RegEdit did the exporting...
I have no answer why RegEdit cannot accurately import its own previous export.
I'm been in listening mode since this post, to learn from those who know far more than I :)
Last edited by RolandJS; 23 Feb 2017 at 10:51.
The original keys were generated by Repetier. I have xfered these keys between my computers in the past without an issue. I don't believe the program changed RE this. The file I uploaded was a reg file that regedit created. Viewing the reg file with notepad showed the LF characters.
Maybe it is something with notepad. I will redo it using ultraedit.
OK, I just exported the Repetier key with all the sub-keys. I then deleted one subkey in the registry and imported the reg file without opening it. All the gcode entries except the gcodeScript#name are missing from the subkey that I deleted. The rest of the entries are there.
Attachment 121731 here is your corrected reg file..
I believe he had WORDWRAP enabled in notepad
or now after reading the ( last page )which I failed to read..
It may of been the program he used did not like spaces / or semi-colons
Just a little FYI:
Qoutes " " are wrapped around commands that have spaces...
Otherwise the command breaks at the space..
Example
Cmd C:\New Folder > is seen as C:\New
Cmd "C:\New Folder" > is seen a C:\New Folder
Thus the give away hint in the first post = quotes all over the place
Thus being read as several single lines of unknown code
rather than a single line of code
@Kyhi
thx, but if I export the key with regedit, delete the key in the registry, then clk the .reg file and import it, I have changed nothing in the .reg file that regedit (a MS program) created. Based on what I saw in notepad previously, I figured there was a problem with those lines, but MS created them, so who am I to question MS...........
So this obviously is a newly created bug from GOD MS, since sometime in the past it worked fine.
well, this issue isn't resolved and the link to the "fixed" file doesn't work.
The registry names that do not import contain CR CR LF at the end of each line in the value
The value in the program that created the entry looks like this
G1 Z5 ; lower bed
G1 X50 Y260 f5000 ; move to back left
G28 Z0 ; test Z0
That is one value for a script name with CRs & LFs
The reg file contains this:
So the 0d 00 0d 00 0a 00 is terminating the " and since that makes it invalid the entry is dropped on import.
So how does the program create it in the first place?
and just eliminating those CR LF is not going to recreate what is in the program.
Just to commiserate a bit, I was 'taught' early in my computing days to never use a word processor program such as Word, Wordpad, WordPerfect, WordPro, etc., to edit such files as the Registry or for programming such as .exe files as there's always hidden coding in the documents but to always use a Text Editor such as Notepad. I haven't tried yet with Notepad++.
I think the question is, what is software do you have registered to open reg?
I have exported a long line, it exported cut by slashes, but it imports OK.
In wordpad, it has added spaces, but even altered, it imports just fine.
So it is most likely you have something messed up with reg classes.
Quote
