If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
The specified file is not a registry script. you can only import binary
On Sat, 23 Jul 2016 11:33:53 +0000 (UTC), Java Jive
wrote: On Sat, 23 Jul 2016 03:19:28 -0400, Micky wrote: Windows Registry Editor Version 5.00 [normally there would be a blank line here] There was. I must have taken it out here for legibility. [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001 But I keep getting the mesage ?The specified file is not a registry script. you can only import binary registry files from within the registry editor?. Windows understands two encodings of *.reg files: ANSI/UTF8 (8 bits, 1 byte per character) Unicode UTF16 (16 bits, 2 bytes per character) By default it saves files in the latter format with a special two-byte value 0xFF 0xFE at the beginning of the file. This message is being I don't know how the average Joe is supposed to know about invisible bytes at the start of the file. caused by the absence of the two-byte value when the *.reg file is in UTF16, or with either encoding by the absence of the first header line ... Windows Registry Editor Version 5.00 ... or possibly also (I'm unsure of this last possibility) the blank line that should follow the above header. When you load a file saved from RegEdit into some editors, the leading two byte value may get stripped out, and if you copy'n'paste from a web page it won't be inserted. That probably has a lot to do with it. And yet everyone who read that article copied the "file" from the webpage and I doubt many knew what you're talking about here. You know this worked for me a year or two ago, with none of this trouble. I probably didn't even post about it because it went smoothly iirc, so I have no record. I can't remember how I did it though. You can get round this by (re-)saving the edited file as ANSI/UTF8. I had resaved it as ANSI. Didn't work. BTW, that's why I spelled ASCII with one i. I meant ANSI. But after I read this post I looked at other options. XP, at least for this type of filel, gives 4 choices: ANSI Unicode Unicode big endian Huh!! I never heard of that! UTF-8 I chose Unicode because it was next in line, and it worked!!! And I looked at it in the registry and it looks right. It would be nice to try the other two choices but I don't want to look for trouble!!! Who is the big endian, and is he Sioux or Cherokee? |
Ads |
#2
|
|||
|
|||
The specified file is not a registry script. you can only import binary
The previous post had to do with adding a field (key, whatever) to the XP registry to trick it into updating until spring of 2019 as if it were an embedded Point of Sale (iirc) version of XP, which are still being supported by MS. I had a reason for asking in win7, oh yeah, that there is a longer version with 2 or 3 other sections, depending on how you count, and the guy who posted that said he got it on alt.windows7.general, though that part of it never panned out. But I posted the solution here. [Default] On Sun, 24 Jul 2016 01:44:59 -0400, in microsoft.public.windowsxp.general Micky wrote: On Sat, 23 Jul 2016 11:33:53 +0000 (UTC), Java Jive wrote: On Sat, 23 Jul 2016 03:19:28 -0400, Micky wrote: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001 But I keep getting the mesage "The specified file is not a registry script. you can only import binary registry files from within the registry editor". Windows understands two encodings of *.reg files: ANSI/UTF8 (8 bits, 1 byte per character) Unicode UTF16 (16 bits, 2 bytes per character) By default it saves files in the latter format with a special two-byte value 0xFF 0xFE at the beginning of the file. This message is being I don't know how the average Joe is supposed to know about invisible bytes at the start of the file. caused by the absence of the two-byte value when the *.reg file is in UTF16, or with either encoding by the absence of the first header line ... Windows Registry Editor Version 5.00 ... or possibly also (I'm unsure of this last possibility) the blank line that should follow the above header. When you load a file saved from RegEdit into some editors, the leading two byte value may get stripped out, and if you copy'n'paste from a web page it won't be inserted. That probably has a lot to do with it. And yet everyone who read that article copied the "file" from the webpage and I doubt many knew what you're talking about here. You know this worked for me a year or two ago, with none of this trouble. I probably didn't even post about it because it went smoothly iirc, so I have no record. I can't remember how I did it though. You can get round this by (re-)saving the edited file as ANSI/UTF8. I had resaved it as ANSI. Didn't work. BTW, that's why I spelled ASCII with one i. I meant ANSI. But after I read this post I looked at other options. XP, at least for this type of filel, gives 4 choices: ANSI Unicode Unicode big endian Huh!! I never heard of that! UTF-8 I chose Unicode because it was next in line, and it worked!!! And I looked at it in the registry and it looks right. It would be nice to try the other two choices but I don't want to look for trouble!!! Who is the big endian, and is he Sioux or Cherokee? |
#4
|
|||
|
|||
The specified file is not a registry script. you can only import binary
In message , R.Wieser
writes: Micky, Who is the big endian, and is he Sioux or Cherokee? That "big endian" and its counterpart, "little endian" refer to the order in which the bytes of a multi-byte value are stored. Take for instance a simple two-byte value like 0x1234. It can be stored in memory using the bytes ordered like 0x34 0x12 , or in the reverse order, 0x12 0x34. The first method is called little endian (as it starts with the lowest-value byte), while the latter one is called big endian (as it starts with the highest-value byte). [] Though the terms were adopted by early rather literate computer folk, with a sense of humour, from a much earlier source (-:. Gulliver's Travels (by Jonathan Swift IIRR), although a good adventure yarn, was also a dig at various political matters of the time it was written (many of which are of course still around): in this case, people who argue quite heatedly about things that are not, really, important. In Lilliput (the land of the tiny people), Lemuel Gulliver encountered two political groupings, the big-endians and the little-endians - whose main difference of opinion, and the reason for their names, was which end of their breakfast boiled egg they broke into. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf "Who came first? Adam or Eve?" "Adam of course; men always do." Victoria Wood (via Peter Hesketh) |
Thread Tools | |
Display Modes | |
|
|