Take the following start menu entry:
command: %programfiles%\Media Tools\MPlayer\mplayer.exe
parameters: ?dvd://1 -dvd-device %p
The %p is converted to 'F:\' (mind the trailing backslash) and mplayer really doesn't like that, it expects simply 'F:'.
Also, when trying to play a DVD-video copied onto hard disk and the path contains spaces, there are no quotes around the expanded path when using %P (please don't tell me I need to use %p and DOS features in XP era and year 2006).
Also, I know this is not one of the greatest features in mplayer (and this may be considered a bug on their side), but hell, this is not the only case, there are no standards concerning the problem (and who would follow them if they were ?) and having one more parameter that sends dir paths without the backslash at the end wouldn't hurt.
%P parameter too strict
Moderators: white, Hacker, petermad, Stefan2
%P parameter too strict
TC for Linux please!
Re: %P parameter too strict
Yeagh, i guess a parameter without the trailing slash might be good.roentgen666 wrote:Take the following start menu entry:
command: %programfiles%\Media Tools\MPlayer\mplayer.exe
parameters: ?dvd://1 -dvd-device %p
The %p is converted to 'F:\' (mind the trailing backslash) and mplayer really doesn't like that, it expects simply 'F:'.
Well, we'll tell you that! There are still some programs out there which may look and work in a modern way but their authors have not given them the ability to understand the meaning of spaces in the command line. Some may treat the whole command line as a long filename and others treat the spaces as parameter separators, so these TC options are still very useful.roentgen666 wrote:Also, when trying to play a DVD-video copied onto hard disk and the path contains spaces, there are no quotes around the expanded path when using %P (please don't tell me I need to use %p and DOS features in XP era and year 2006).
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3
x64: Clients/Servers from Win7 to Win11 and Win2K12Srv to Win2K22Srv, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3
x64: Clients/Servers from Win7 to Win11 and Win2K12Srv to Win2K22Srv, mainly Win10 though.
2wanderer
TC included . But that is not problem here as I don't think there are programs that understand paths that contain spaces without quotes around them.Well, we'll tell you that! There are still some programs out there which may look and work in a modern way but their authors have not given them the ability to understand the meaning of spaces in the command line.
TC for Linux please!
only if they accept 1 parameter (filename)roentgen666 wrote:2wandererTC included . But that is not problem here as I don't think there are programs that understand paths that contain spaces without quotes around them.Well, we'll tell you that! There are still some programs out there which may look and work in a modern way but their authors have not given them the ability to understand the meaning of spaces in the command line.
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3
x64: Clients/Servers from Win7 to Win11 and Win2K12Srv to Win2K22Srv, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3
x64: Clients/Servers from Win7 to Win11 and Win2K12Srv to Win2K22Srv, mainly Win10 though.
- majkinetor !
- Power Member
- Posts: 1580
- Joined: 2006-01-18, 07:56 UTC
- Contact:
- majkinetor !
- Power Member
- Posts: 1580
- Joined: 2006-01-18, 07:56 UTC
- Contact: