Mail Archives: djgpp/2008/02/23/04:30:08
Jim Michaels wrote:
> Jim Michaels wrote:
>> lbinstdj constantly says on startup that numeric tails are disabled,
>> and that numeric tails should be turned on. then it wants to run
>> onnumtl.reg.
>> no matter how many times I reboot and do this process, it still
>> doesn't unpack any of the zip files, even though I have specified
>> where the zip packages are. (pkgs in C:/DJGPP, installing to C:/DJGPP).
>
>
> by the way, the .reg files included appear to create the wrong data type
> in the registry, due to the registry files being written incorrectly.
>
> They create a data type of REG_BINARY instead of REG_DWORD, which is
> probably what should be used. All of the other registry values in that
> subkey have the type REG_DWORD, not REG_BINARY.
>
> instead of the line
> "NameNumericTail"=hex:00
> and
> "NameNumericTail"=hex:01
>
>
> use
> "NameNumericTail"=dword:0
> and
> "NameNumericTail"=dword:1
>
>
>
> please correct the 2 reg files nonumtl.reg, onnumtl.reg, and
> djgpp2\v2faq\faq22_19.html
>
>
>
> oh, and by the way, lbinstdj still complains.
>
I found out why lbinstdj complains. XP and 2000 and vista do not have
this registry value anymore. this is a windows 9x/ME-ism.
check out
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/default.mspx?mfr=true
the windows 2000 server resource kit online. (I don't have the money
right now for the XP Pro resource kit
http://www.microsoft.com/mspress/books/6795.aspx, but it should have
been in the 2000 kit!)
http://support.microsoft.com/kb/q179370/
is the link to the kb article which talks about numeric tails registry
entry in win9x/ME systems, and has a link to an article about how
numeric tails are generated in win9x/ME/NT systems.
please fix the program.
I think the unzipper program needs to be a 32-bit console app for NT
family systems *and* there needs to be an OS detection thing in place.
(that's as easy as checking the environment variables for OS=Windows_NT
so that's covered.
actually, I don't know how the installer does its detection. hopefully,
it tries this by actually detecting/deleting/creating some temp files
and checking for uniqueness, rather than checking for a registry value
(might be worth a try). because apparently on an NT family system, that
registry value isn't going to do anything.
--
Jim Michaels
for email, edit the address
- Raw text -