Jump to content











Photo
- - - - -

*.ini association mystery.


  • Please log in to reply
1 reply to this topic

#1 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 May 2012 - 04:03 PM

In multiPE I created a notepad++ script and associated *.ini, *.txt, *.log with it.

While this works fine in a PE2 and PE3, in a PE1 it works with *.txt and *.log only.
For *.ini Notepad.exe is used.

When I check wit RegEditWB, all command lines are defined correctly when building the target:

"...NotepadPPNotePad++.exe" "%1"


In the running PE1 in the registry the command for *.ini is just "notepad.exe %1"

I need your experience with that.
Do you know whether explorer during boot sets some defaults?
If yes, how can I avoid this "feature"?

Peter

#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 May 2012 - 04:26 PM

I found it. The good old historic notepad.script by smiley does not really belong to the class of "Cooperative Scripts".

I'll modify notepad.script.

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users