VB script to kill all PC Suite processes

Hello :-)
You know how some PC Suite components hang when the connection with the phone is interrupted? And how you have to log off and back on to clear it?
I got fed up of doing that so knocked up this VB script and called it "PC Suite kill.vbs". Snappy name, eh? Maybe I should take up copywriting.
It's developed and tested (= hacked together) with PC Suite 6.7.0.22 on Windows XP Pro SP2. Please back up all your data and lock your daughters away before trying it at home. Guaranteed no registry hacks.
If you try "PC Suite kill.vbs" on another version of PC Suite and Windows and it doesnt kill PC Suite and all its components it's probably because the "path names" of the programs are different. To solve this problem there's another VB script below, snappily named "Get info on all processes.vbs", that should give the pathnames on your computer. You have to start PC Suite and whichever component(s) are not being killed then run "Get info on all processes.vbs, look in C:\temp.txt for the pathnames and copy-and-paste them into your copy of "PC Suite kill.vbs".
Feedback appreciated -- would be nice to make "PC Suite kill.vbs" detect the PC Suite version and Windows version and adapt itelf accordingly.
Here come the scripts. No file attachment facility on this board so they're in the message. Beware split lines.
=== "PC Suite kill.vbs" starts ===
' Nokia PC Suite kill
' Usage:
' * No options or arguments
' * Developed and tested with PC Suite 6.7.0.22 and Windows XP Pro SP2
' 30may06 Charles Atkinson
' * Quick and dirty to kill all PC Suite processes.
' Written because parts of PC Suite hang if the connection with the phone is interrupted
' Acknowledments to Hans-Georg Michna (www.michna.com/nokia6230.htm) for the idea and .BAT example
' Wishlist
' * Detect PC Suite and Windows versions and modify behaviour to suit
' * Cope with %systemroot% being other than C:
Option Explicit
' Declare constants
Const strComputer = "."
' Declare variables
Dim intCounter
Dim intProcessNamesIdxMax
Dim objProcess
Dim objShell
Dim strProcessNames(14)
' Initialise variables
strProcessNames(1) = "C:\PROGRA~1\COMMON~1\PCSuite\Services\SERVIC~1.EXE"
strProcessNames(2) = "C:\PROGRA~1\COMMON~1\Nokia\MPAPI\MPAPI3s.exe"
strProcessNames(3) = "C:\PROGRA~1\COMMON~1\PCSuite\DATALA~1\DATALA~1.EXE"
strProcessNames(4) = "C:\PROGRA~1\COMMON~1\PCSuite\Services\SERVIC~1.EXE"
strProcessNames(5) = "C:\Program Files\Nokia\Nokia PC Suite 6\ApplicationInstaller.exe"
strProcessNames(6) = "C:\Program Files\Nokia\Nokia PC Suite 6\AudioManager.exe"
strProcessNames(7) = "C:\Program Files\Nokia\Nokia PC Suite 6\ConnectionManager.exe"
strProcessNames(8) = "C:\Program Files\Nokia\Nokia PC Suite 6\ContentCopier.exe"
strProcessNames(9) = "C:\Program Files\Nokia\Nokia PC Suite 6\ImageConverter.exe"
strProcessNames(10) = "C:\Program Files\Nokia\Nokia PC Suite 6\ImageStore.exe"
strProcessNames(11) = "C:\Program Files\Nokia\Nokia PC Suite 6\LaunchApplication.exe"
strProcessNames(12) = "C:\Program Files\Nokia\Nokia PC Suite 6\MultimediaPlayer.exe"
strProcessNames(13) = "C:\Program Files\Nokia\Nokia PC Suite 6\OneTouchAccess.exe"
strProcessNames(14) = "C:\Program Files\Nokia\Nokia PC Suite 6\PcSync2.exe"
intProcessNamesIdxMax = 14
' For each process
For each objProcess in GetObject( "winmgmts:" ).InstancesOf( "Win32_Process" )
' Compare with each known PC Suite process
For intCounter = 1 To intProcessNamesIdxMax Step 1
' And if it matches
If strProcessNames( intCounter ) = objProcess.ExecutablePath Then
objProcess.Terminate
Exit For
End If
Next
Next
Wscript.Quit 0
=== "PC Suite kill.vbs" ends ===
=== "Get info on all processes.vbs" starts ===
' Get info on all processes
' Usage:
' * No options or arguments
' * Output to C:\temp.txt
' * Developed and tested with Windows XP Pro SP2
' 30may06 Charles Atkinson
' * Quick and dirty to get info on all processes.
' Written to get full path names for PC Suite processes for "PC Suite kill and restart.vbs"
' Declare constants
Const intForWriting = 2
' Open text file for writing
Set objFSO = CreateObject( "Scripting.FileSystemObject" )
Set objTextFile = objFSO.OpenTextFile( "C:\temp.txt", intForWriting, True )
' For each process ...
for each objProcess in GetObject( "winmgmts:" ).InstancesOf( "Win32_Process" )
strCreationDate = Mid(objProcess.CreationDate,7,2) & "/" & Mid(objProcess.CreationDate,5,2) & "/" & Left(objProcess.CreationDate,4) & " " & Mid(objProcess.CreationDate,9,2) & ":" & Mid(objProcess.CreationDate,11,2) & ":" & Mid(objProcess.CreationDate,13,2)
objTextFile.WriteLine( objProcess.ProcessId & "," & objProcess.ParentProcessId & "," & strCreationDate & "," & objProcess.Name & "," & objProcess.ExecutablePath )
next
' Close file and exit
objTextFile.Close
Wscript.Quit 0
=== "Get info on all processes.vbs" ends ===
Nokia 5130c-2

You can download the scripts from here.
They have extension .txt to comply with Yahoo's restrictions. You'll need to change it to .vbsMessage Edited by catkin on 06-Jun-2006
12:47 PM
Nokia 5130c-2

Similar Messages

  • Looking for a script to kill all inactive sessions

    Does anyone have a script to kill all INACTIVE sessions (with EXECUTE IMMEDIATE)?

    I suggest you to specify which OS you are talking about.
    The inactive status on the V$SESSION doesn't mean the user is not doing any thing, it only means the oracle server process is not processing any thing by the time it was queried. On OLTP systems Oracle Server Processes remain INACTIVE for more than 95% of the time, so it is advisable to configure shared servers.
    If you are really concerned about idle time, then I suggest you to configure profiles.
    On the pool mechanism you should address the microsoft side, if this, as far as I understood and guessed, application server is IIS.
    I suggest you further reading on the Killing sessions script and different session status (check the sniped status) here:
    Re: session inactive ??
    Re: make a job to delete the sniped sessions
    Re: How do I put a timeout in my DataBase?
    Re: Killing Session with Locks in Linux
    ~ Madrid

  • Scripts for killing blocking oracle processes?

    We are having a problem in that when a user disconnects improperly, the oracle processes on our Oracle Apps box don't die properly and rows remain locked. For other terminal based versions, the script to kill the process is pretty simple, but for the web-based, java interface, it's unclear how I would go about doing this. Does anyone have scripts for doing this that could run via cron? The applications are running on solaris 2.6.
    Thanks,
    Nathan Olla
    Unix Sys Admin

    Take a look at note 130709.1 on Metalink. It contains configuration info for httpds.conf - your Apache configuration file. You can use this to time-out sessions properly. Hope this helps.

  • Restart of SOA Suite server = Manually restart all running BPEL processes?

    Hi,
    Is it true that in SOA Suite 10.1.3 you have to manually restart all running BPEL process if you restart the SOA Suite? And that this was working in 10.1.2?
    If it is true, how do people handle that? We might have thousands of processes waiting in Waiting state on the server so this sounds like a nightmare. :-)
    Regards Pete

    Yes, I was a bit surprised too, that is why I am asking. :-) I was a colleague that told me that it was not working in 10.1.3. But I should just go and check it out.
    Regards Pete

  • XServe and 10.5 won't boot..."syncing disks killing all processes"

    Hey Everybody,
    Have an Xserve Intel Quad-Core Xenon 2.8 GHz, 80gb, 2 Gb RAM. 10.5 Server.
    2 Gb of RAM has been anemic. The server runs a few Cold Fusion Web Sites, DNS, OD, FTP, AFP, and Mail Services. Our mail is not light duty as we send out almost daily 70,000 e-mails to our customers.
    Last week I added 2 x 4gb DIMM to bring up the RAM to 10 Gb. I added the RAM to slots 3 & 4. Saw great improvement right away. The night after, I noticed the server rebooted during the night. (Didn't look into why )
    Well, I came in this morning and was checking up on the server (via ARD) and couldn't connect. Went to the server room and saw the machine was off. Not good. I restarted it and went back to my office. Checked again on ARD, and still wasn't available. Went back to server, rebooted in verbose mode (after booting with a monitor and seeing the screen show the apple with the spinning gear) and It's hanging then shutting down within three minutes of boot.
    Attached is a pic of what is shown, at around 3 minutes from boot the screen will then say "syncing disks killing all processes" and the server shuts down.
    I've googled all morning and have tried various methods to boot to no avail.
    I removed the RAM that I added and the problem persists. I also removed the drive sled and reinserted it into the xserve and also tried bay 2.
    Other things...
    Yesterday added two more web sites and the DNS for it in Server Admin.
    Any suggestions? Bad drive?
    Shaun

    OK, having exactly same issue - but on a much older and much less duty machine. Dual G4 1Ghz running 10.5 Server. Noticed that I could not connect via ARD and did hard shutdown, notice identifier light was on as well. The system did reboot as I could get my mail, but when I connected a monitor to it all I had was gray screen.
    Did another hard shutdown after pressing IL and not just gets to logo and spinning wheel for a short while and shuts down.
    It has been up and running flawlessly for long time prior to this.
    My name is Sean too, maybe that is the issue...

  • Killing all sessions at once who are locking the objects

    Hello all,
    i am working in 9i Oracle RDBMS on AIX IBM OS
    most of the time we face locking issue and there comes more then different 50 sessions which locking different tables.
    here is my script to find out what sessions are locking what tables.
    set lines 200
    set pages 50000
    col SID for 99999
    col SERIAL# for 999999
    col username format a12
    col sql format a55
    col event format a50
    col program format a40
    col MINS for 9999
    col ID1 for 999999
    col object_name for a35
    col locktype for a8;
    select  /*+ ORDERED */ s.sid,s.serial#,s.status,round(s.last_call_et/60) MINS,s.program,l.ID1,d.object_name,d.object_type,l.type as locktype
    from v$lock l,v$session s, dba_objects d
    where l.sid = s.sid
    and l.ID1 = d.object_id
    and s.username = 'MULDMS'
    and last_call_et > 120 and l.type <> 'TX' order by s.status,MINS,l.ID1,l.type; and the out put it gives something like
      SID SERIAL# STATUS    MINS PROGRAM                                      ID1 OBJECT_NAME                         OBJECT_TYPE        LOCKTY
    8981    1069 ACTIVE       2 frmweb@Appsdms31 (TNS V1-V3)               30407 VH_BTN                              TABLE              TM
    1642     512 ACTIVE      15 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
      690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
      699    1787 ACTIVE      17 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
      690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
      690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                      TABLE              TM
    10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
    6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    1912    1655 ACTIVE      18 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
    6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    1912    1655 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    1754    1582 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     30643 VT_CHECK_INOUT                      TABLE              TM
    6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                      TABLE              TM
    10708     982 ACTIVE      19 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    5428     855 ACTIVE      19 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    10708     982 ACTIVE      19 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    5428     855 ACTIVE      19 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    10278     897 ACTIVE      20 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
    6261    1056 ACTIVE      20 frmweb@appsdms12 (TNS V1-V3)               28846 AM_DOCS                             TABLE              TM
    6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
    1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    10278     897 ACTIVE      20 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
    6261    1056 ACTIVE      20 frmweb@appsdms12 (TNS V1-V3)               30407 VH_BTN                              TABLE              TM
    1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    3521     717 ACTIVE      20 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
    6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     30643 VT_CHECK_INOUT                     TABLE              TM
    1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                   TABLE              TM
    9131    1002 INACTIVE     2 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
    4887    1040 INACTIVE     2 [email protected] (TNS V1-V3)     30455 VH_PSF                              TABLE              TM
      151    1982 INACTIVE     2 [email protected] (TNS V1-V3)     80224 RD_ENQEXD                           TABLE              TM
      846     988 INACTIVE     3 [email protected] (TNS V1-V3)    29228 GM_VIN                              TABLE              TM
    5364    1149 INACTIVE     3 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    9934     789 INACTIVE     3 [email protected] (TNS V1-V3)     30455 VH_PSF                              TABLE              TM
    7511    1092 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
    3595    1104 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
      846     988 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
      945     670 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TMand then i have to kill the session one by one . thaat is a tedious task to do.
    i want to modify this script which will give me all the kill statement and i just have to run it
    can someone help me in this regard as i am weak in sql/plsql
    thanks and many thanks

    >
    i want to modify this script which will give me all the kill statement and i just have to run it
    >
    Karthick's script will 'kill' the sessions but before you use that script you may want to read the docs about the KILL and DISCONNECT clauses.
    See the DISCONNECT SESSION and KILL SESSION clauses in the SQL Language doc
    http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm#sthref4724
    >
    DISCONNECT SESSION Clause
    Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever).
    The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
    KILL SESSION Clause
    The KILL SESSION clause lets you mark a session as terminated, roll back ongoing transactions, release all session locks, and partially recover session resources.
    IMMEDIATE Specify IMMEDIATE to instruct Oracle Database to roll back ongoing transactions, release all session locks, recover the entire session state, and return control to you immediately.
    >
    For DISCONNECT the IMMEDIATE clause will recover the session state 'immediately'.
    Using KILL, even with the IMMEDIATE clause, you are telliing Oracle to roll back any ongoing transactions and that can take a lot of time.
    Make sure you are really doing the operation you want to do. If you want to get the locks released immediately you need to use 'DISCONNECT IMMEDIATE'.

  • Script to stop all weblogic instances running on a box

    Hi,
    Is there any script to stop all instances of weblogic running on a Unix box at once?
    My understanding is grep for weblogic processes and then issue kill -9 .
    Correct me if im wrong and also provide the right script to shutdown all weblogic instances.
    Thanks!!

    Hi,
    You can use simple JMX code to achieve the same (Shutting down all the Servers present inside a Domain at once) :
    Topic: Force Shutingdown WLS Using JMX
    http://middlewaremagic.com/weblogic/?p=55
    NOTE: The above JMX code is intended to just shut down the AdminServer you can remove the if {} block from from Line No -60 the following JMX code to shutdown all the Servers rather than shutting down Only the Admin Server.
    Thanks
    Ravish Mody

  • Script to kill blocking sessions

    We use Oracle 10. We have a test database used solely for training and I need the give the trainer the ability to kill all the blocking sessions when a block(s) is holding up
    the entire class.
    My idea was to create a simple form on our Oracle menu- containing just a single button that when pressed would trigger the script. One press of the button
    to kill each and every blocking session. I have no clue as to how to write a script of this nature. Would appreciate any advice.
    Regards,
    Sandy

    This is easier said than done. Numerous reasons. Here's a couple:
    You cannot rely on using v$session to identifying blocked sessions.
    Some user sessions may be blocked by a system process (e.g. log writer), which means you cannot unblock the user sessions by killing the blocking session. (especially when running into an Oracle bug where a user session will spin on "+enq: RO - fast object reuse+" when dropping an object and then being shown as blocked by a system session/process).
    Killing a session in Oracle is a misnomer as the "+alter system kill session+" is a request and not a command. The relevant user session needs to terminate itself (kind of like assisted suicide). No other process actually kills the physical process (or thread) executing that user session. Thus if that user session is waiting on some external response or event, it will be unable (now and forever) to respond to that kill request. In such a case, the only alternative is killing the physical process instead. (or shutting down the database)
    A blocking session could be a job process that contains problematic code that leads to the blocking/serialisation. Killing that session will simply fail the job after which the job queue manager will restart the session again.. 16 times in succession. Only then will it mark that job entry as broken and cease trying to restart it.
    So killing blocking sessions? It is not easy to identify blocking processes, they cannot always be killed, and even when you do kill them, they may simply reincarnate as a new session.
    So what is the solution then?
    Blocking sessions are not "+A Bad Thing+". There are very good and technically sound reasons for serialisation. When it does become a problem, there's something more to it. And blindly killing blocking sessions in such a case is treating the symptom of a problem and ignoring the problem all together. Find the reason for this serialisation and address that.

  • Can I have "All spots to process" checked at all times, even for new spot colors?

    When I check “All spots to process” in the pdf export settings and save my settings the settings remember that I've checked this option. But, if new spot color objects using new spot color swatches are added to the document (or another document) and I go into the pdf export settings the check mark has been changed into a dash (with the actual checkbox highlighted) – signifying that only some of of the spot colors will be changed to process colors during export. I absolutely fail to see how this could possibly be seen as a feature and not a bug … if the user has checked “ALL spots to process” wouldn't the user expect ALL spots to be converted to process colors, rather than just any spot colors that happened to be in the document that happened to be open when the user first checked that checkbox and saved that setting?
    Am I missing something here? What's the point of even having that checkbox as part of your saved export settings if it doesn't include any other spot colors than those used when saving the settings?
    What's the point of having settings if you can't trust them, and still need to manually "override" them every time?
    I see that some users have taken to writing scripts that instead turn all spot colors in the swatch panel to process colors, and while I commend them for creating that workaround, I'm still pissed at Adobe for not getting the function right.
    If this is a feature, who is it for? People who want to add just certain spot colors and turn those into process colors rather than turning all spot colors into process colors are surely better off doing that in the swatches panel, where they're in total control of what's what. And if they don't want to "permanently" change their spot colors to process colors, and prefer to (temporarily) convert them during exporting/printing only, they can do that in the ink manager. But when someone checks convert "All spots to process" couldn't we safely assume they really want ALL spot colors to be converted and not just some of them? I mean, the way that checkbox behaves now, it's like it's a button and not a checkbox. As in: hit the button "All spots to process" to switch all currently viewed spot colors to process colors in the ink manager, OR check the "All spots to process" checkbox to always convert ALL spot colors to process colors during exporting/printing.
    Anyone got any light to shed on this?
    And is there a way to actually get the advertised behavior, because if you have to run a script every time you export/print you might as well just manually select the checkbox every time instead, but either way it's just really unnecessary as far as I'm concerned … Adobe should get the feature right instead.
    If you save a setting and recall it, it shouldn't be possible for that setting to change into something else (in this case changing a checkmark to a dash).
    Clearly CMYK printing is the norm, so for most users it would make a lot of sense to have the "All spots to process" checked most of the time, and then you just go into the swatches panel or the ink manager and set things correctly for those print jobs that really do need spot colors.
    I myself am not one of those who add spot colors to my swatches unless I'm really using them as spot colors, but I often work with magazines and folders featuring adverts made by whoever, and typically there's always at least one advert that features spot colors, and therefore it would be very nice if the "All spots to process" feature actually worked as advertised without any required actions from me.
    We stopped sending ads back to the advertisers for adjustments a long time ago, unless we absolutely had to, because there were so many things wrong with so many ads that it was simply too much work to write back and explain everything to people who most of the time didn't even understand what we were talking about. We found that it was usually a LOT faster and easier to just adapt the ads ourselves, as long as it was something that could be worked out really quickly from within InDesign itself, which pretty much included most typical errors.
    But with this feature I find Adobe is trying to make my job harder rather than easier, and it's pissing me off. Arrrghh… ;-)

    But It's not a preference it's a shortcut
    It's a bad joke, is what it is. ;-)
    So, why in your opinion should it be presented the way it is? I keep saying in it's current functionality it shouldn't be presented the way it is (and that: if it is, it shouldn't work the way it does). If it's not a preference or even a proper checkbox, why present it that way?
    If you put it right next to the table at the top of the window (so that it's directly associated with that information, rather than information right above it) and just called the checkbox “Spot(s) to process” and had it only visually reflect the content of the sleected spot colors in the table, then I'd see your point with likening it to the “Hyphenate” checkbox.
    If a story has two selected paragraphs that uses two different hyphenation settings then the checkbox should present the way it does now, but if you hit the checkbox so that both paragraphs now use hyphenation and create a third paragraph inbetween the two previous ones it better inherit that setting and not turn off hyphenation for the new paragraph (unless of course there's a defined next paragraph style that switches to a style with hyphenation turned off). And if that checkbox said “Hyphenate all paragraphs” instead, then I would expect it to do just that, and not just the selected ones, and not just the current paragraphs but quite literally all paragraphs even newly created ones – otherwise it doesn't do what it says it does, and simply shouldn't be labeled that way.
    And seriously bad interface design aside, you'd have to rename “All spots to process” to “Switch all currently displayed spot swatches listed in the table above to process” to actually describe what that checkbox does. So even if you're a fan of the current functionality, as opposed to one that actually lets the user set and forget a setting like that, and think it's better that users manually check it repeatedly (which I'm not saying that you are, but you're not giving me any feedback suggesting you even see my point of view with any of this, so what do I know?), then why wouldn't you still support an interface that visually matches/signals that functionality better? If it's a “Select all” checkbox supplementing a table containing a column of checkboxes, then present it that way. Don't put it at the bottom of the window next to another checkbox that works just like a regular checkbox and label it “All spots to process” – because that way you are signalling a different behavior.
    Seriously, if I was to do design using the same mentality that Adobe uses when designing their user interfaces it wouldn't be long before I lost all clients. There's a lot to be said for de facto monopolies, I suppose. Oh no, there's nothing wrong with the design, just as long as you accept it on it's own terms and don't compare it to anything relevant, and just as long as you give people enough time to understand and accept it … and surrender to it.
    For real … I wouldn't win one single pitch that way.
    Today's threads have in many ways been a thorough reminder of the following quote from the second link I provided:
    Is there an Internet rule yet stating that even the most obviously indefensible mistake will eventually be defended by someone somewhere? Awful marketing efforts get explained as genius viral campaigns, broken features become solutions.
    And whether or not you're able to see my point of view or not is really besides the point too.
    The real point was, and remains to be:
    That for those who receive lots of ads or other external files that may or may not contain spot colors it would be far more useful to be able to set a checkbox to always convert all spots to process when exporting, than the current functionality is (and I'm not suggesting eliminating the current functionality, just change so it's presented like what it really is, and then just let that separate checkbox do what it says) … causing unnecessary manual action on the user's behalf shouldn't be the business of Adobe – preventing it should.
    And here's further reading on the subject of bad Adobe interface design for those who might feel so inclined. ;-)
    Cheers!

  • What differences if we kill SMON or we kill  PMON Back ground processes ??

    Hello
    i am little bit confused.Please help me out...
    If we kill PMON---->Instance crashed---->Alert log content
    LGWR (ospid: 9764960): terminating the instance due to error 472
    Instance terminated by LGWR, pid = 9764960
    If we kill SMON---->Instance crashed---->Alert log content
    PMON (ospid: 13041666): terminating the instance due to error 474
    Instance terminated by PMON, pid = 13041666
    2010-12-27 07:31:04.187000 +01:00
    Then ,what is the difference in mechnism in killing either to SMON or PMON???

    Oh..wait...I just asked this question due to curiosity about what happen INTERNALLY when we kill any BG process(specially mandatory).
    For testing..I kill all the process in each attempt and found some similar and some different lines in alert log.
    Kill PMON:
    LGWR (ospid: 9764960): terminating the instance due to error 472
    Instance terminated by LGWR, pid = 9764960
    Kill CKPT:
    PMON (ospid: 6553606): terminating the instance due to error 469
    2010-12-27 12:08:51.650000 +01:00
    Instance terminated by PMON, pid = 6553606
    Kill SMON:
    PMON (ospid: 13041666): terminating the instance due to error 474
    Instance terminated by PMON, pid = 13041666
    Now,is any knowledge about these error nos(472/469/474) ???
    What happen internally when we kill PMON or SMON ??

  • 'All spots to process' Checked automatically. Please help

    Hi,
    I recently sent a job to print which was supposed to have 1 spot colour. It came back from the printer 4-colour with no spot and when I ckecked the artwork 'All spots to process' was checked in the Ink Manager.
    I definitely did not check the box as I wasn't even aware of it and previous versions of the document show it was un-checked.
    Is it possible to turn this feature on by default/automatically/by accident!? Could I have activated it elsewhere in InDesign?
    Thanks
    Ian

    Hi lan,
    Me also faced same problem i think this will be helpful to you
    Just run the script before exporting the pdf file all spot colors will coverts as a CMYK
    Say BIG "thank you" to Jongware. This is his script
    app.activeDocument.colors.everyItem().properties = {space:ColorSpace.CMYK, model:ColorModel.PROCESS};
    For more details see below link
    http://forums.adobe.com/thread/732362?tstart=0
    Regards,
    Siva

  • How to use a script to kill only forms sessions idle for over 30 minutes?

    We want to use a script to kill forms users idle for over 30 minutes, but we don't want to kill background concurrent processes waiting for resources. even though we set up the timeout but it won't work for users who exit forms ungracefully.
    thanks!

    Java runs at the serverside, while you need a clientside solution. Javascript is perfectly suitable. Pass the current maxInactiveInterval() value to a Javascript variable and write a function around it. You can use for example the onkeypress attribute of the body to clear the timeout counter.

  • Kill all sessions of a special user

    Hi all,
    I'm not very familar with PL/SQL but I think this will help my on my "issue".
    Sometimes I need to kill all current sessions (most times 36 sessions) of a single database user.
    All sessions have a different sid and serial# and manually executing "alter system kill session 'xxx,yyyy' isn't really funny.
    Im thinking of a small PL/SQL script which receives the dbuser name as parameter and then killing all sessions of the user.
    Could please anyone give ma a hint or a short example on this??
    Many Thanks
    Joerg
    Edited by: Joerg Lang on 22.06.2009 12:38

    Hey Hoek,
    thanks...
    granting "alter system" to my user, by my self :D, let the procedure run without any errors...
    Strange thing and good to know...
    Ok, but now I'm still having the issue when using the "username" as parameter of the procedure.
    create or replace procedure kill_session(user in varchar2)
    is
    begin
    for sessions in ( select sid, serial#
                        from   v$session
                        where  username = 'user_to_kill')
      loop
        execute immediate 'alter system kill session '''||sessions.sid||','||sessions.serial#||'''';
      end loop;
    end;works fine and all sessions are killed.
    create or replace procedure kill_session(user in varchar2)
    is
    begin
    for sessions in ( select sid, serial#
                        from   v$session
                        where  username = '||user||')
      loop
        execute immediate 'alter system kill session '''||sessions.sid||','||sessions.serial#||'''';
      end loop;
    end;works not, but also now errors ar shown..
    any Idea?

  • Script to select all layers based on condition?

    Do anyone have a script to select all layers based on either name or color label? Possibly using search but not necessarily?

    If you search this forum you will find script that will process all layers in a document.  You can modify one if them to skip the layers you do not want to process do nothing to the. The process uses recursion to process layers within layer groups,.

  • All BW dialog processes occupied while loading

    Hi,
    All dialog processes (9) in BW are occupied at loading from the SCAPPTSEG table in CRM.
    We do not have any problem with other loads.
    Has anybody a solution for this?
    rgds,
    Marcel

    Hi Van,
    Its not a good practice to kill the job in production.
    First check if the PID for that particular process is progressing or waiting for the gate way of some other reason.
    this you can check in SM50 - local work process overview of the systems.
    Also check for the system log in SM21 transaction...
    check if there are any short dumps...
    capture all the inforamtion and check with BASIS if the PID is processing or not and if not processing and HUNG you can take help of BASIS to Kill the PID. the process will be terminated.
    Regards
    KP

Maybe you are looking for

  • My phone wont let me turn wifi on

    my phone turned wifi off itself and when i try to turn it back on it wont let me. the button remains grey and off

  • Where to check SAP version in server

    Hi, I am new to SAP and I would like to know how can I check my SAP version in development server whether it is R/3, mySAP or Netweaver 2004s, SP stack 8 and my Enterprise portal version. I know that it is 4.7, is it R/3? Does it mean that if my comp

  • Simple Select on VBPA using index running very slow

    Hello, We have a very simple selection on the table VBPA: data: begin of it_vbeln occurs 100,   vbeln like vbpa-vbeln, end of it_vbeln. select vbeln from vbpa into table it_vbeln where kunnr = '##########' and parvw = 'AG'. All we're trying to accomp

  • Deletion of auth objects Corresponding to tcodes

    Q1. If a transaction is deleted from the menu wthr the Corresponding authorization objects are deleted. Q2.Eg What if the tcode MM02 is deleted from the role which has MM01/MM02/MM60/MM03 transaction codes, In this case some of the auth objects of MM

  • Transformation routine for Infoobject lookup

    Hey guys, I am aware of Update rule routines but never done Transformation routine before. I didnt get any related post for my req. My requirement is on WBS element I have some attributes which is coming from std WBS Attr extractor but I have one cus