[XP] Thread priority bij snelkoppeling instellen

Pagina: 1
Acties:
  • 109 views sinds 30-01-2008
  • Reageer

  • harlekein
  • Registratie: Maart 2002
  • Laatst online: 04-05 14:48

harlekein

Creator Owner

Topicstarter
Is het mogelijk om een programma te starten en daar een extensie voor te gebruiken zodat deze in een gekozen priority wordt gestart?

Ik heb wel gezien dat het onder command gaat dmv \low, \realtime, etc, maar in een snelkoppeling werkt dat niet.

  • Aetje
  • Registratie: September 2001
  • Laatst online: 18-12-2025

Aetje

Troubleshooting met HAMERRR

Bij een snelkoppeling het command arguement aanpassen?

Forget your fears...
...and want to know more...


  • harlekein
  • Registratie: Maart 2002
  • Laatst online: 04-05 14:48

harlekein

Creator Owner

Topicstarter
Dat werkt dus niet. Je kunt onder command aangeven:
code:
1
\low C:\progra~1\blaat\blaat.exe


Dat werkt. Je kunt dat verhaal ook in een .bat bestand zetten met start ervoor. Maar in een snelkoppeling accepteert windows het niet.

  • harlekein
  • Registratie: Maart 2002
  • Laatst online: 04-05 14:48

harlekein

Creator Owner

Topicstarter
*kick*

  • Aetje
  • Registratie: September 2001
  • Laatst online: 18-12-2025

Aetje

Troubleshooting met HAMERRR

code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
C:\WINNT\system32>start /?
Starts a separate window to run a specified program or command.

START ["title"] [/Dpath] [/I] [/MIN] [/MAX] [/SEPARATE | /SHARED]
      [/LOW | /NORMAL | /HIGH | /REALTIME | /ABOVENORMAL | /BELOWNORMAL]
      [/WAIT] [/B] [command/program]
      [parameters]

    "title"     Title to display in  window title bar.
    path        Starting directory
    B           Start application without creating a new window. The
                application has ^C handling ignored. Unless the application
                enables ^C processing, ^Break is the only way to interrupt
                the application
    I           The new environment will be the original environment passed
                to the cmd.exe and not the current environment.
    MIN         Start window minimized
    MAX         Start window maximized
    SEPARATE    Start 16-bit Windows program in separate memory space
    SHARED      Start 16-bit Windows program in shared memory space
    LOW         Start application in the IDLE priority class
    NORMAL      Start application in the NORMAL priority class
    HIGH        Start application in the HIGH priority class
    REALTIME    Start application in the REALTIME priority class
    ABOVENORMAL Start application in the ABOVENORMAL priority class
    BELOWNORMAL Start application in the BELOWNORMAL priority class
    WAIT        Start application and wait for it to terminate
    command/program
                If it is an internal cmd command or a batch file then
                the command processor is run with the /K switch to cmd.exe.
                This means that the window will remain after the command
                has been run.

                If it is not an internal cmd command or batch file then
                it is a program and will run as either a windowed application
                or a console application.

    parameters  These are the parameters passed to the command/program


If Command Extensions are enabled, external command invocation
through the command line or the START command changes as follows:

non-executable files may be invoked through their file association just
    by typing the name of the file as a command.  (e.g.  WORD.DOC would
    launch the application associated with the .DOC file extension).
    See the ASSOC and FTYPE commands for how to create these
    associations from within a command script.

When executing an application that is a 32-bit GUI application, CMD.EXE
    does not wait for the application to terminate before returning to
    the command prompt.  This new behavior does NOT occur if executing
    within a command script.

When executing a command line whose first token is the string "CMD "
    without an extension or path qualifier, then "CMD" is replaced with
    the value of the COMSPEC variable.  This prevents picking up CMD.EXE
    from the current directory.

When executing a command line whose first token does NOT contain an
    extension, then CMD.EXE uses the value of the PATHEXT
    environment variable to determine which extensions to look for
    and in what order.  The default value for the PATHEXT variable
    is:

        .COM;.EXE;.BAT;.CMD

    Notice the syntax is the same as the PATH variable, with
    semicolons separating the different elements.

When searching for an executable, if there is no match on any extension,
then looks to see if the name matches a directory name.  If it does, the
START command launches the Explorer on that path.  If done from the
command line, it is the equivalent to doing a CD /D to that path.

C:\WINNT\system32>

Ik denk dat het wel gaat lukken met dit... Verander het commando naar START "Commandline" /HIGH voor succes.

Forget your fears...
...and want to know more...


  • harlekein
  • Registratie: Maart 2002
  • Laatst online: 04-05 14:48

harlekein

Creator Owner

Topicstarter
Aha! Vanuit de Windows/system32 proberen. Dan zou de snelkoppeling wel geldig moeten zijn ja. Ik ga het testen zodra mijn systeem weer werkt. ([rml]Device in "[ PM7] Aantal vragen"[/rml])

  • harlekein
  • Registratie: Maart 2002
  • Laatst online: 04-05 14:48

harlekein

Creator Owner

Topicstarter
Start (.exe, bat oid) is niet te vinden in de Windows directory.

  • Aetje
  • Registratie: September 2001
  • Laatst online: 18-12-2025

Aetje

Troubleshooting met HAMERRR

C:\Windows\Command voor 95/98 systemen
Winnt systemen hebben ze blijkbaar niet, maar het commando is wel geldig.

Forget your fears...
...and want to know more...

Pagina: 1