Jump to content

DAMN NFO Viewer 2.10 RC3


Judas989
 Share

Recommended Posts


I will never understand why people use this thing... notepad with terminal size 9 works fine for me.

it's a nice gui and i preffer left my notepad at default font :P

@Judas989 it doesn't need any regkey, only associate .nfo files with it, so compress it and extract to a "utilities" folder.

Link to comment
Share on other sites

Export everything in these keys:

[HKEY_CLASSES_ROOT\.nfo]

[HKEY_CLASSES_ROOT\****.NFO.Viewer.File]

[HKEY_CURRENT_USER\Software\****\**** NFO Viewer]

Merge them all in one reg file.

Copy **** NFO Viewer from Program Files to C:\XPCD\$OEM$\$Progs\ and execute the reg file somewhere in your unattended setup :)

The only prompt you get when you try to open an nfo file is the viewer asking to be the default viewer.

Link to comment
Share on other sites

the reg file

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.nfo]@="****.NFO.Viewer.File"

[HKEY_CLASSES_ROOT\****.NFO.Viewer.File]

@="**** NFO Viewer file"

[HKEY_CLASSES_ROOT\****.NFO.Viewer.File\DefaultIcon]

@="C:\\PROGRA~1\\DAMNNF~1\\DAMNNF~1.EXE,1"

[HKEY_CLASSES_ROOT\****.NFO.Viewer.File\shell]

@="open"

[HKEY_CLASSES_ROOT\****.NFO.Viewer.File\shell\open]

@="Open in &**** NFO Viewer"

[HKEY_CLASSES_ROOT\****.NFO.Viewer.File\shell\open\command]

@="\"C:\\PROGRA~1\\DAMNNF~1\\DAMNNF~1.EXE\" \"%1\""

[HKEY_CURRENT_USER\SOFTWARE\****]

[HKEY_CURRENT_USER\SOFTWARE\****\**** NFO Viewer]

"Language"=dword:00000409

"Version"="2.10.0031"

"MaxFileSizeKb"=dword:000001f4

"CheckDefaultViewer"=dword:00000001

"ReuseWindow"=dword:00000001

"AlwaysOnTop"=dword:00000000

"WorkingDirectory"="I:\\Kylie_Minogue-Chocolate-DVDRiP-SVCD-2004-PmV\\"

[HKEY_CURRENT_USER\SOFTWARE\****\**** NFO Viewer\NFO]

"FontName"="[built-in] Terminal"

"FontData"=hex:8f,00,00,01

"Window"=dword:00000023

"BackgroundColor"=hex:ff,ff,ff,00

"TextColor"=hex:00,00,00,00

"HyperLinkColor"=hex:7a,96,df,00

"HyperLinkHoverColor"=hex:00,54,e3,00

"Text"=dword:00000400

[HKEY_CURRENT_USER\SOFTWARE\****\**** NFO Viewer\WindowPlacements]

"Main"=hex:2c,00,00,00,02,00,00,00,03,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,\

  ff,ff,ff,ff,ff,ff,42,00,00,00,57,00,00,00,5e,02,00,00,02,02,00,00

 

[HKEY_CLASSES_ROOT\.diz]

"PerceivedType"="text"

@="****.NFO.Viewer.File"

[HKEY_LOCAL_MACHINE\SOFTWARE\****]

[HKEY_LOCAL_MACHINE\SOFTWARE\****\**** NFO Viewer]

@="C:\\PROGRAM FILES\\**** NFO Viewer"

Link to comment
Share on other sites

  • 1 month later...
  • 3 weeks later...

Although I found the AutoIT installer to work correctly before testing in either VirtualPC/VMWare or infact trying the CD itself and ironing out the problems later. I found that although installations like that may work on your development machine or the same machine that you install your unattended CD/DVD on like in my case, the installer doesn't always behave exactly as tested.

Therefore, I'm going to install this application with the information that has already been provided, especially since this is the only installer that I can think of which I have to automate using AutoIT. I do however install the applications which have an .msi installer with /QB, at least until I get an almost perfect unattended CD.

That maybe a bit of wishful thinking on my part, since newer versions of the applications I install come out fairly regularly (normally just after I've finalised a specific revision of my CD), but there’s no harm in trying I suppose. :)

Link to comment
Share on other sites

Since the site that I downloaded it from doesn't have a .msi available to install it with, I can only assume that someone else made it from the installer that they downloaded.

The only way someone could do that would be to use a program such as WinINSTALL LE and using the discover wizard. That will record any changes made to the computer both before and after installation and creates a .msi file including the newly copied files and a .reg file recording any changes made to the registry.

Aaron has the right idea for installing this, since a program this small isn't really worth the effort for creating a .msi installer for, in my opinion anyway. :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...