Inventory internal components
Is there a command, script or program available that will tell me what PCI boards, disks, memory, etc are installed in my server?
Are you running Solaris? The Solaris prtconf command man page synopsis begins like this " The prtconf command prints the system configuration information. The output includes the total amount of memory, and the configuration of system peripherals formatted as a device tree ". Perhaps this tool will help, read the rest of the man page.
Similar Messages
-
How do I install the International Components for Unicode (ICU) libraries?
I am trying to build a program with requires the ICU libraries and it's unclear to me how to install them.
The only ICU-related fink package I can see is libicu32-dev. I installed that but then afterwards when I run icu-config I get an error. For example:
$ icu-config --cppflags
### icu-config: Can't find /usr/lib/libicuuc.dylib - ICU prefix is wrong.
### Try the --prefix= or --exec-prefix= options
### or --detect-prefix
### icu-config: Exitting.
The fink description for libicu32-dev says it contains "Headers for Apple-supplied ICU libraries". So should these libraries already be on my OS X machine, or do I need to get them from somewhere else?Sounds like a fink bug to me. The package assumes you only need the headers and that the libraries are already installed - but they are not. You haven't lost them - I checked my machine for the library it looks for. Maybe the fink package should be specific to another version of OS X? Or something else went wrong?
I'd try asking the fink people about it as it looks like a port problem.
- cfr -
Inventory Control of new houses (construction and sale)
Colleagues,
Need information about controlling inventory of new homes, the business process is from the construction and sale, but using the traditional solution of SAP ECC 6.0, not EC&O
Thanksit sounds like you have a slow database server, or one that is sending the
data over a WAN link. When you deleted the database, it had to recover all
the information in the STR files. Normally, delta scans are done every day
or so to see if anyting has changed, and then a full scan every five days.
I would bump this up to 20 since usually there very few workstations that
will need a full scan.
For you boss, I would suggest that you nicely inform him that the inventory
pulled by ZfD is at least 80% accurate but never 100%. If you have a
workstation that is not being scanned, registered, imported, etc.. you are
likely to miss it. How do you account for the WS Removal policy which will
pull out inventory when the machine is not registered for "x" days. If
anything, use the ZfD inventory as a backup for internal components only.
Good Luck,
Ken Puett, CNE,CNI
> We are running zenworks 4 ir7 on nw6 sp5. Installed it a number of years
> ago mostly for the purpose of remote control of systems. Inventory got
> installed but never paid attention to it. Now my boss wants accurate
> reports on workstations and what was in the inventory was definitely not
> accurate. Deleted the database files (sybase) and started over. It
> appears to be working but very slowly. After a week and a half it has
> discovered 248 systems. Is this normal? Was this originally setup wrong?
> Any advice is appreciated
>
> Thanks
>
> James -
MRP planning components at multiple plants
I would like to present a unique scenario, we have a plant and a warehouse both are created as two different plants in SAP.
When we run MPS/MRP at a Finished product (FERT) level at the mfg plant, I would like to
1) Consume inventory of components (Packaging material - VERP) at the plant first
2) It should then consume inventory of packing material from warehouse
3) Only then it must creates a procurement proposal for the remaining qty at the mfg plant.
4) There shall not be procurement proposals created at a warehouse, all proposals should be directed to the plant.
Most of them would advice to create the warehouse as a storage location within the manufacturing plant but that is not possible due to financial reasons.
Flood me with ideas.Hi Manoj
The standard MRP cannot consider stock in different plants for the same material.
Please observe that this issue has been already discussed on several thread on this forum. Check for example my answer on the thread below:
MRP Run considering Stocks for Multiple Plants and Requirement maintained for Plant Cluster
BR
Caetano -
Configuration of internal PI 7.0 communications to use https
I am looking for some clear documentation on how to do this. I have read through the documentation discussing this but it does not specifically tell you the steps. This is the type of verbiage I have found:
"The components of a process integration (PI) landscape communicate with each other for different purposes like configuration, administration, monitoring, or the actual messaging.
In addition to proper messaging, technical communication between various PI tools and runtime components is required.
Two different technical protocols are used for these communications: HTTP and RFC. Both the technical and the business communication are described together with the used protocols in the following two sections:
I've gotten this from this link:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/fb/322f41d606ef23e10000000a155106/content.htm">SSL configuration</a>
This link describes in detail the communication that takes place:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/5e/f85141196ff423e10000000a155106/content.htm">Technical communication PI 7.0</a>
I think from this list of Exchange Profile this is how I would enable SSL internally (set port any way):
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/6f1741b393f26fe10000000a1550b0/content.htm">Exchange Profile parameters - connections is relevant</a>
Is this where I should change the port numbers? Where do I activate the https for communication between internal components? Are there any ABAP stack (SM59) connections to change? Any help is greatly appreciated. Thanks.George,
Have you seen this weblog:
/people/rahul.nawale2/blog/2006/05/31/how-to-use-client-authentication-with-soap-adapter
Also you have to enable this. Check this help:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2e7020d-0d01-0010-269c-a98d3fb5d16c
http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm
---Satish -
Cap file Components size limit ( ? )
Hello,
I'm wondering if there is a limitation on the Cap file internal components size.
as specified in the JVM Spec from SUN, a cap file consists on several elements (byte sequences) : Header.cap , Class.cap, StaticField.cap, etc.
Does a component have a size limit ?
I'm asking this question because I'm facing serious problem when loading Applets on Gemplus SIM cards(GemWpressoV3 ) : the load process interrupts sudenly and the card responds with 6F00 !!
For info, the Method.cap components is 11748 bytes !!
Thank you for your Help and Info
Kartagoshere is a complete description of the Cap I can't load :
Header.cap (29 Bytes)
Directory.cap (34 Bytes)
Import.cap (62 Bytes)
Applet.cap (23 Bytes)
Class.cap (94 Bytes)
Method.cap (8484 Bytes)
StaticField.cap (6312 Bytes)
ConstantPool.cap (925 Bytes)
RefLocation.cap (1411 Bytes)
Descriptor.cap (2340 Bytes) -
Advanced drawing of components
Hey all,
I have yet to see a really good book that explains in detail the various capabilities of the Graphics 2D. There are tons of capabilities, like Shape and all its subclasses, Transform, the many methods of Graphics2D, and so on. There are some VERY kick-ass possibilities yet it seems very few people understand how to use these more advanced features of Graphics2D.
As an example, I am trying to create a nice rounded, shadowed panel component with a gradient shadow and definable rounded corners with a definable arc. For the most part, it hasn't been difficult doing the rounded stuff, but trying to get the shadow just right, faded on the rounded curve, and so on has not been easy. I have tried many things, from using fillRoundRect, to fillArc, to looking at using clipping and compositing, possibly a Shape object, etc. I am no graphics expert, so the lack of docs/tutorials that explain how to really use the Graphics2D and all of its capabilities is disappointing. I almost feel I need to be a 2D/3D expert to understand the various features.
So, does anyone have any good links, or book suggestions that really explain Graphics2D and really delve into advanced drawing features, such as creating custom drawn components? Are there some free resources on the net to help out? If not, I will be happy to buy a good book or two.
I want to learn how to use Shape, Compositing, clipping, gradients, transforms, text and fonts, strokes, and so forth in good detail, enough that I can answer a good deal of questions posted in this forum and others and know how to attack a problem like a rounded shaded cornered panel component.
Speaking of, one concern I have with making a rounded panel is how to enforce that components added to the panel are within the inside rounded edges. Is this the job of insets()? I thought of using an internal panel and delegating all the add(), find(), get(), remove() and other methods of the JPanel that I extend (or JComponent), to the internal panel. I have also tried drawing the shadowed portion as a border, so that perhaps (hopefully) I dont need an internal panel component, as that seems a bit messy. But I surely don't want any components to be added that overlap the rounded edges. Any ideas on this?
ThanksI have been thinking about using it as a border
instead of drawing it as a complete component. I think
that would allow the internal components to be added
to the panel without much fanfare of the rounded
border, although it may still pose a problem should
the rounded edges and shadow take up more space than
they should. I don't know much about insets, but I am
hoping by adjust the insets that the add() methods
would use those to place components within the inset
range and not the entier 0,0,width,height of the panel
itself.That's the job of the layout manager -- if it is stretching components to fill a panel, it should
know about the (left, top, bottom, right) gaps of the insets as dictated by the border and place
components not within rectangle (0, 0, width, height) but within rectangle
(left, top, width-left-right, height-top-bottom).
That being said, I wish I had a nickel for every time I read someone's custom component method,
where their paintComponent assumes that can draw at (0,0) -- no realizing they have to offset for the
insets of the border!
A demo that shows GridLayout knows about borders:
import java.awt.*;
import javax.swing.*;
import javax.swing.border.*;
public class ExampleBorder implements Border {
private int thickness;
private Color color;
ExampleBorder(int thickness, Color color) {
this.thickness = thickness;
this.color = color;
public Insets getBorderInsets(Component c) {
return new Insets(thickness, thickness, 0, 0);
public boolean isBorderOpaque() {
return false;
public void paintBorder(Component c, Graphics g, int x, int y, int width, int height) {
Color oldColor = g.getColor();
g.setColor(color);
if (width > thickness)
g.fillRect(x, y, width-thickness, thickness);
if (height > thickness)
g.fillRect(x, y, thickness, height-thickness);
g.setColor(oldColor);
//convenience
public JComponent wrap(JComponent comp) {
Border old = comp.getBorder();
if (old == null)
comp.setBorder(this);
else
comp.setBorder(BorderFactory.createCompoundBorder(this, old));
return comp;
//sample main
public static void main(String[] args) {
ExampleBorder panelB = new ExampleBorder(6, Color.BLUE);
ExampleBorder compB = new ExampleBorder(2, Color.RED);
JPanel cp = new JPanel(new GridLayout(2, 2, 1, 1));
//cp.setBorder(BorderFactory.createEmptyBorder(2,2,2,2));
panelB.wrap(cp);
cp.add(compB.wrap(new JButton("alpha")));
cp.add(compB.wrap(new JButton("beta")));
cp.add(compB.wrap(new JButton("gamma")));
cp.add(compB.wrap(new JButton("delta")));
JFrame f = new JFrame("X");
f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
f.setContentPane(cp);
f.pack();
f.setLocationRelativeTo(null);
f.setVisible(true); -
Assignment of G/L on Maintenance Order Internal Component
Hi,
I can specify G/L of my choice on Maintenance Order (PM Maintenance Order) for external components ( Non Stock Items) but unable to do so for Internal Components(Stock Items). Is there any configuration which could allow me to specify G/L of my choice for an internal component attached on a Maintenance Order?Lets take a scenario
Suppose i have got some stock in my store, the time i bought them i was not sure where i m going to use them..i have three departments Admin, IT and Production. That particular stock item can be utilized in either of three categories. The purpose of giving my own GL on Maintenance Order was to see the utilization of that stock item under the head for which the Maintenance Order was created i.e.
if the maintenance activity is being performed in Admin the usage of the material should managed under GLs of Admin. By the way, does it really make sense ? -
Window that can automatically grow to show all of its components
Try as I might, I cannot get a window to automatically grow so that all of its internal components are properly visible. I've tried messing with bindings but apparently a lot of prefWidths and the like aren't calculated until a component is actually visible. Window.sizeToScene also doesn't really appear to do anything. Essentially I'd just like to be sure when a window is shown that everything is visible. Is there an easy way to do this? Any advice would be appreciated, thanks.
Wow, it turns out the answer is shockingly simple but it's not really clear from the documentation. If you use the Scene constructor that does not take width,height parameters ( http://docs.oracle.com/javafx/2.0/api/javafx/scene/Scene.html#Scene(javafx.scene.Parent) ) then your Scene will be big enough. Awesome!
-
Installing a bigger internal hard drive
Hello...I have a MacBook Pro with only 80 GB of internal memory....I am thinking of increasing this memory to something around 200GB...What is a good brand name that I should go for...I can't find anything on the Apple site. And is it something that I can do or it is pretty much complicated...I am a newbee but I understand the basics basically...Thanks for any help...
Installing a hard drive yourself inside a MacBook Pro is not recommended. You can damage the internal components inadvertently if you don't know what you are doing. Upon finding a non-authorized configuration change, AppleCare has in the past been known to balk at repairing machines under AppleCare's own cost that had hardware installed that wasn't authorized. Under what conditions they do or don't is not something we can really discuss here as it is clearly something Apple has its own policy that users can only read from through the AppleCare protection plan documentation. I strongly recommend you read that in the http://www.apple.com/support/ website. Sometimes you can get an authorized service center to install it for you and make sure your warranty is not affected. I would call around and find out which may be able to do that.
You would be looking for a 2.5" SATA notebook hard drive by Seagate or Western Digital. All are pretty good. And don't be put off by the slower speed, as the tracks are narrower, making seek time less even with less RPMs. -
hi all,
i need to design flow chart for checking for a program whether it satifies the abap coding standards or not. who to do it. if possible send me graphical representations [flow charts] or links to find programming standards.
some of my requirements in that folw chart are
1. how to recognize a blank space in a given program,
2. how to recognize a comment,
3. how to check wheteher a keyword is used or not,
4. how to identify the ' :' symbol
thanks & regards,
suresh babu aluri.plz go through this documementaion,
i think its helpful.
ABAP Programming StandardsContents
1. Objective 5
2. Naming Conventions 5
2.1 Codes for naming conventions 5
2.1.1 Module Codes 5
2.1.2 Free text 6
2.2 Naming Convention of Development Objects 6
2.2.1 Package 6
2.2.2 Executable Program 6
2.2.3 BSP Application 7
2.2.4 Logical Database 8
2.2.5 SAP Scripts /Smartforms 9
2.2.6 Idocs 9
2.2.7 Transaction Code 10
2.2.8 Function Groups 10
2.2.9 Dictionary Objects 11
2.2.10 Message Class 11
2.2.11 Enhancement Projects (User Exits) 11
2.2.12 LSMW Objects 12
2.2.13 Classes 12
2.2.14 BOR Object Types 13
2.2.15 Screen / Transaction Variants 13
2.2.16 Area Menu 13
2.3 Naming of Sub-Objects 13
2.3.1 Program Sub-Objects 13
2.3.2 SAP Script /Smartform sub-objects 14
3. General Programming Guidelines 14
3.1 Modification Logs 14
3.2 Program Organization 15
3.2.1 Executable Programs 15
3.2.2 Dialog Programs 15
3.3 Package 15
3.3.1 Adding Components to existing objects 15
3.3.2 Creation of New Objects 15
3.4 Program Messages 15
3.4.1 Adding Messages to existing landscapes 15
3.4.2 Creation of New Objects 16
3.5 Dictionary Objects 16
4. Structure of ABAP Programs 16
4.1 Type 16
4.2 Status 18
4.3 Authority Check 18
4.4 Program Structure 19
4.4.1 Declaration data for global data, classes and selection screens 19
4.4.2 Container for Processing Blocks 19
4.4.3 Calling Processing Blocks 20
4.5 Screen Flow Logic (Dialog Programs) 20
4.5.1 Place the AT EXIT COMMAND at the beginning of the flow logic. 20
4.5.2 Use FIELD and CHAIN statements to keep fields in error open for correction. 20
4.6 Main Program 20
4.6.1 Events 20
5. General Coding Standards 21
5.1 One command per line 21
5.2 Indented Source Code 21
5.3 Extended Syntax Check 21
5.4 Reusability and Modularity 21
5.5 Text Handling 21
5.6 Usage of System Variables 22
5.7 Chaining Statements 22
5.8 Common Routines 22
5.9 Dialog Messages 22
5.10 Function Keys 23
5.11 Enqueuing and Dequeuing Data Objects 23
5.12 Error Handling (SY-SUBRC) 23
5.13 General Conventions and Hints 24
5.14 Parameters in Sub-Routines 24
6. Performance Standards 25
6.1 General Tips on Performance Tuning 25
6.1.1 Avoid Redundant code 25
6.1.2 Subroutine Usage 25
6.1.3 Case vs. Nested IF 25
6.1.4 Using the MOVE Statement 25
6.1.5 SELECT Queries 25
6.1.6 Using the READ statement 27
6.1.7 Hashed table 27
6.1.8 Transporting 28
6.1.9 Using LDB 28
6.1.10 Append Lines of 28
6.1.11 Use WHILE 28
6.1.12 DELETE <itab> WHERE 28
6.1.13 Using WHERE clause in LOOP .ENDLOOP 28
1. Objective
The objective of this document is to describe general programming guidelines, methodologies, Naming conventions and performance guidelines for all the programs developed for SAP Project.
2. Naming Conventions
This chapter describes the naming conventions to be followed for naming the programming objects for SAP project.
2.1 Codes for naming conventions
The variable portion of naming convention is given with Code ID given in angle brackets(<>). Use the following tables for replacing code IDs with codes in the object naming.
2.1.1 Module Codes
Code ID: mm
Code Description
FI Finance
CO Controlling Module
MM Materials Management
PP Production Planning
SD Sales & Distribution
QM Quality Management
PM Plant Maintenance
IM Inventory Management
WM Warehouse Management
BC Basis Module
BW Business Warehouse
WF Workflows (Master Data Management)
HR Human Resources
EBP EBP
PS Project Systems
PCP Synpro: Product Costing
PAP Synpro: COPA
DP APO : Demand Planning
SP APO : Supply Network Planning
DS APO : Production Planning & Detailed Scheduling
AT APO : Global ATP
TP APO : Transportation Planning/Vehicle Scheduling
CI Core Interface
LC Live Cache
2.1.2 Free text
Code ID: ffff
Developer should replace ffff with meaningful text. The text can be multiple words separated by underscore.
2.2 Naming Convention of Development Objects
2.2.1 Package
Naming Convention: Z<mm>_<ffff>.
Notes:
1. Replace <mm> with Module codes given in section 2.1.1 above.
2. Replace <ffff> with the sub-landscape of the Module that this Message Class caters to as illustrated in examples below.
3. The maximum permissible length for development class is 30 characters
Examples:
Dev. Class Description
ZFI_AR FI: Account Receivables
ZCO_CCA CO: Cost Center Accounting
2.2.2 Executable Program
Naming Convention: Z<mm>_<ffff>.
Notes:
1. Replace <mm> with module codes given in section 2.1.1 above.
2. Replace <ffff> with meaningful text as illustrated in examples below.
3. The maximum permissible length for program name is 30 characters. However, the name should be restricted to 25 characters to accommodate appropriate Include naming as described in 2.2.2.
Examples:
Program Name Description
ZFI_VAT_RET FI: Report for VAT Return
ZMM_AUTO_GR MM: Automated Goods Receipt
ZSD_XX_STCK_SHORTAGE SD: Stock shortage report for stock allocation
2.2.2.1 Includes for executable programs
Naming Convention: Z<mm>_<ffff>_<Inn>.
Notes:
1. All includes of executable program will be prefixed by Z, followed by the same program name as described in 2.2.2 above.
2. Replace <Inn> with include type and sequence number. Use the following table for includes.
Include Type ID Description
TOP Top Include.
Fnn Subroutine pool (Forms)
Inn PAI Modules
Onn PBO Modules
Xnn Other Includes
The maximum permissible length for Include name is 30 characters.
Examples:
Include Name Main Program Name Description
ZFI_VAT_RET_TOP ZFI_VAT_RET FI: Report for VAT Return Top Include
ZFI_VAT_RET_F01 ZFI_VAT_RET FI: Report for VAT Return Forms
ZMM_AUTO_GR_TOP ZMM_FR_AUTO_GR MM: Automated Goods Receipt Top include
ZMM_AUTO_GR_F01 ZMM_FR_AUTO_GR MM: Automated Goods Receipt Forms
2.2.3 BSP Application
2.2.3.1 Main Application
Naming Convention: BSP Applications shall follow the same Naming Convention as Executable Programs i.e. Z<mm>_<ffff>.
Notes:
1. Replace <mm> with module codes given in section 2.1.1 above.
2. Replace <ffff> with meaningful text as illustrated in examples below.
2.2.3.2 Pages & Controllers
Naming Convention: <ffff>
Notes:
1. Replace <ffff> with meaningful text, that adequately describes the function of the page/controller
2.2.3.3 Theme
Naming Convention: Z_<ffff>.
Notes:
1. Replace <ffff> with meaningful text
2.2.3.4 Mime Objects:
Naming Convention: <ffff>
1. A MIME Object can be logo for the company.
2. Replace <ffff> with meaningful text, that adequately describes the function of the MIME objects
2.2.3.5 Controller and Handler Classes:
See section Classes (Section 2.2.133)
2.2.3.6 BSP Extension
Naming Convention: Z_<ffff>
Notes:
1. Replace <ffff> with meaningful text
2.2.3.7 BSP Layout elements id
Label: lb_fffff
Input field: if_fffff
Button: b_fffff
Text Edit: te_fffff
Text View: tv_fffff
Radio button Group: rbg_fffff
Radio button: rb_fffff
Check Box Group: cbg_fffff
Check Box cb_fffff
Tray tr_fffff
Tabstrip ts_fffff
Tableview tab_fffff
1. Replace <fffff> with meaningful text
2.2.4 Logical Database
Naming Convention: Z<mm>_<ffff>.
Notes:
1. Replace <mm> with module codes given in section 2.1.1 above.
2. Replace <ffff> with meaningful text
3. The maximum permissible length for LDB name is 20 characters. However, the name should be restricted to 15 characters to accommodate appropriate Include naming
4. LDB Program and LDB Program Includes shall follow the naming convention Auto-Generated by SAP
2.2.5 SAP Scripts /Smartforms
Naming Convention: ZF<mm>_<ffff>.
Notes:
1. Replace <mm> with module codes given in section 2.1.1 above.
2. Replace <ffff> with meaningful text as illustrated in examples below.
Examples:
Form Name Description
ZFFI_EMP_CONF Employee Confirmation Letter
ZFFI_ANN_TO Annual Turnover Letter To Customers and Vendors
2.2.6 Idocs
2.2.6.1 Idoc Types
Basic Type :
Naming Convention : ZB<FFFF>NN
Notes:
1.Replace <NN> with sequence number.
3. Replace <ffff> with meaningful text.
Extension Type : ZX<Basic type name>_NN
Notes:
1. Replace <NN> with sequence number .
2.2.6.2 Message Types
Naming Convention : ZM<mm><ffff>.
Notes :
1. Replace <mm> with module codes given in section 2.1.1 above.
2. Replace <ffff> with meaningful text .
2.2.6.3 Process Code
Naming Convention : Z<ffff>.
Notes :
1. Replace <ffff> with meaningful text ..
2.2.6.4 IDOC Segments
Naming Convention : Z1<ffff>.
Notes :
1.Replace <ffff> with meaningful text as illustrated in examples below.
2.2.7 Transaction Code
Notes:
1. The tcode name is provided by SAP TIN The Developer must write a mail to SAP Tin asking for the T-Code name with a filled form.
The form can be found at :
2.2.8 Function Groups
Naming Convention: Z<mm><ffff>
Notes:
1. Replace <mm> with relevant module code as given above
2. Replace <ffff> with meaningful text.
2.2.8.1 Function Group Include Programs
Naming Convention: LZ<Function Group><Inn>.
Notes:
1. All includes of Function Group program will be prefixed by LZ, followed by the Function Group name
2. Replace <Inn> with include type and sequence number. Use the values from the table given in 2.2.2.1
Examples:
Include Name Function Group Name Description
SAPLZMMPURCHASING ZMMPURCHASING F.Group-Purchasing: Main Program
LZMMPURCHASINGO01 ZMMPURCHASING F.Group-Purchasing: PBO
LZMMPURCHASINGI01 ZMMPURCHASING F.Group-Purchasing: PAI
LZMMPURCHASINGF01 ZMMPURCHASING F.Group-Purchasing: Forms
LZMMPURCHASINGTOP ZMMPURCHASING F.Group-Purchasing: Data Declarations
2.2.8.2 Function Modules
2.2.8.2.1 Normal Function Modules
Convention: Z_<mm>_<ffff>.
Notes:
1. Replace <mm> with relevant module code as given above.
2. Replace <ffff> with meaningful text.
2.2.8.2.2 IDOC Function Modules
Convention: Z_IDOC_<mode>_<msg type>.
Notes:
1. Replace <mode> with INPUT or OUTPUT depending on whether the function processes incoming or outgoing IDOC.
2. Replace <msg type> with the IDOC message type.
2.2.9 Dictionary Objects
Tables: Z<mm><ffff>
Structures: ZS<mm><ffff>
Views: ZV<mm><ffff>
Data Element: ZDE<mm><ffff>
Domain: ZDO<mm><ffff>
Table Type: ZTT<mm><ffff>
Type Group: Z<ffff>
Search Help: ZSH<mm><ffff>
Lock Object: EZ<mm><ffff>
Notes:
1. Replace <mm> with module code given above.
2. Replace <ffff> with meaningful text.
2.2.10 Message Class
Naming Convention: Z<mm>_<ffff>.
Notes:
1. Replace <mm> with Module codes given in section 2.1.1 above.
2. Replace <ffff> with the sub-landscape of the Module that this Message Class caters to as illustrated in examples below.
3. The maximum permissible length for development class is 30 characters
Examples:
Msg. Class Description
ZFI_AR FI: Account Receivables
ZCO_CCA CO: Cost Center Accounting
2.2.11 Enhancement Projects (User Exits)
Convention: Z<XX><nn>.
Notes:
1. XX is the application area code e.g. for sales it is SD etc.
2. 'nn' is one up number for one application area. It starts with 001.
3. Maximum length of the Project name is 8.
Example: The name of the SD enhancement project can be ZSD001.
2.2.12 LSMW Objects
2.2.12.1 Project
Naming Convention: ZM_<ffff>.
Notes:
1. 1. Replace <ffff> with meaningful text
2. The maximum permissible length for Project name is 16 characters. But please limit it to 12.
Example : ZM_VENDOR
2.2.12.2 SubProject
Naming Convention: ZM_<ffff>_<n>.
Notes:
Suffix Project name with a running sequence no.
Example : ZM_VENDOR_1
2.2.12.3 Object
Naming Convention: ZM_<ffff>_<n><n>.
Notes:
Suffix Subproject name with a running sequence no.
Example : ZM_VENDOR_11
2.2.13 Classes
Naming Convention: ZCL_[IM/DF/BSPCO/BSPHN/BADI]_<ffff>.
1. IM: Implementation Class;
DF: Definition Class
BSPCO: BSP Controller class
BSPHN: BSP Handler class
BADI : BADI implementation
2. Replace <ffff> with meaningful text: In case of Implementation classes, it should preferably be the same as that of the Definition Class
3. Example:
IMPLEMENTATION Class: ZCL_IM_REBATE_SETTL
DEFINITION: ZCL_DF_REBATE_SETTL
2.2.14 BOR Object Types
Object Convention Example
Supertype Z<ffff> ZLVAPPL
SubType Z<SuperType><nn> ZZLVAPPL01
Program <Subtype> ZZLVAPPL01
1. Replace <nn> with a running 2 digit serial Number
2. Replace <ffff> with meaningful text
2.2.15 Screen / Transaction Variants
Naming Convention: <tcode>_<ffff>
Where:
1. Replace <tcode> with the t-code that will be assigned to this Variant
2. Replace ffff with a meaningful text
E.g.:
For an SE16 variant for table KONA that will be used by T-Code Z_CH_SD_001:
Z_CH_SD_001_KONA
2.2.16 Area Menu
Naming Convention: Z<mm>_<Main Menu>_<Sub Menu> <ffff>
Where:
1. Replace <mm> with the Module code
2. Followed by the hierarchical position of the immediate parent of this Area Menu
3. Followed by a Meaningful text for this Menu
E.g.:
ZSD
ZSD_TAB
ZSD_TAB_VIEW
ZSD_TAB_UPDT
Notes:
1. Clusters of Transactions should be introduced as Sub-Menus rather than as Folders
2. As a gradual process, the current Clusters that exist as Folders should also be replaced with Sub-Menus
2.3 Naming of Sub-Objects
2.3.1 Program Sub-Objects
Naming of all the internal components of a program will be consistent across the project.
Naming Convention: <Prefix>ffff.
Notes:
1. Replace <Prefix> with the component prefix values given in the table below.
Program Component Prefixed by
Program Constants C_
Global Variables W_
Types Definition T_
Global Structures WA_
Global Internal Tables I_
Select-Options SO_
Parameters PO_
Table Type TT_
Field Symbols FS_
Ranges R_
Local Constants LC_
Local Variables L_
Local Static Variables LS_
Local Internal Tables LI_
Local Work Area LWA_
Local Range LR_
Field Groups FG_
Container CO_
Macro MA_
Important: The Same sequence as above must be followed in the Data declaration part of all the ABAP/4 programs.
2.3.2 SAP Script /Smartform sub-objects
Naming of all the internal components of a SAPScript/SmartForm shall follow the same convention as for Programs (2.2.2), with the addition of the Field Label on the FRS. E.g. if the FRS has labeled a field for Sales Order Number as Field 27 on the Layout, the variable name should be W_27_VBELN.
3. General Programming Guidelines
3.1 Modification Logs
At the top of every ABAP Object Modified by a Developer, there should be a Modification Log Every Line Created/Changed by the developer should be Identifiable by the TR Number.
ABAP Patterns: Following Patterns should be used for Uniform ModLogs:
Nature of Change Pattern to Use
New Development ZZNEWPROG
In-Line Logs ZZLINE
Modification Logs at the Top of Object ZZMODLOG
3.2 Program Organization
All the programs will be organized as described below.
3.2.1 Executable Programs
TOP Include: For global data declarations
Form Include: For definition of all the FORMs.
3.2.2 Dialog Programs
TOP Include: For global data declarations
Form Include: For definition of all the FORMs.
PBO Include: Include for PBO Modules
PAI Include: Include for PAI Modules
3.3 Package
All the related objects within a sub-module of SAP will be developed under a single Package.
3.3.1 Adding Components to existing objects
When adding new workbench components to existing Objects, the same Package will be used as has been used for the existing Components
3.3.2 Creation of New Objects
When creating new Objects or new Sub-lanscapes, Packages used should have the Naming convention as in Section 2 Above
3.4 Program Messages
All the messages within a sub-module of SAP will be grouped under a single Message Class.
3.4.1 Adding Messages to existing landscapes
When adding new messages for existing Objects, the same Message Class will be used as has been used for the existing Objects
3.4.2 Creation of New Objects
When creating new Objects or new Sub-landscapes, Message classes used should have the Naming convention as in Section 2 Above
3.5 Dictionary Objects
Whenever you create a Z table in system always include MANDT field as the first field, except when the table contains client independent data. Also create the table with attribute Data Class as USER.
4. Structure of ABAP Programs
4.1 Type
When an ABAP program is run, its processing blocks are called. ABAP programs are controlled from outside the program itself by the processors in the current work process. For the purposes of program flow, we can summarize the screen processor and ABAP processor into the ABAP runtime environment. The runtime environment controls screens and ABAP processing blocks. It contains a range of special control patterns that call screens and processing blocks in certain orders. These sections are also called processors. When a ABAP program is run, the control passes between various processors.
In the R/3 System, there are various types of ABAP program. The program type determines the basic technical attributes of the program, and must be set when created. The main difference between the different program types is the way in which the runtime environment calls its processing blocks.
When an application program is run, it must at least call the first processing block from outside the program, that is, from the runtime environment. This processing block can then either call further processing blocks or return control to the runtime environment. When an ABAP program is started, the runtime environment starts a processor (dependent on the program type), which calls the first ABAP processing block.
The following program types are relevant to application programming:
Type 1
Type 1 programs have the important characteristic that they do not have to be controlled using user-defined screens. Instead, they are controlled by the runtime environment, which calls a series of processing blocks (and selection screens and lists where necessary) in a fixed sequence. User actions on screens can then trigger further processing blocks.
Type M
The most important technical attribute of a type M program is that it can only be controlled using screen flow logic and run via a transaction code which is linked to the program and one of its screens (initial screen).
ABAP programs with type M contain the dialog modules belonging to the various screens. They are therefore known as module pools.
Type F
Type F programs are containers for function modules, and cannot be started using a transaction code or by entering their name directly.
Type F programs are known as function groups. Function modules may only be programmed in function groups. The Function Builder is a tool in the ABAP Workbench that is used to create function groups and function modules. Apart from function modules, function groups can contain global data declarations and subroutines. These are visible to all function modules in the group. They can also contain event blocks for screens in function modules.
Type K
Type K programs are containers for global classes in ABAP Objects. Type K programs are known as class definitions. The Class Builder is a tool in the ABAP Workbench that can be used to create class definitions.
Type J
Type J programs are containers for global interface in ABAP Objects. Type J programs are known as interface definitions and are created in the Class Builder.
Type I
Type I programs - called includes - are a means of dividing up program code into smaller, more manageable units. The coding of an include program can be inserted at any point in another ABAP program using the INCLUDE statement. There is no technical relationship between include programs and processing blocks. Includes are more suitable for logical programming units, such as data declarations, or sets of similar processing blocks. The ABAP Workbench has a mechanism for automatically dividing up module pools and function groups into include programs.
4.2 Status
P = SAP standard production program
K = Customer production program
S = System program
T = Test program
Application
Categorize the program according to the purpose it fulfills.
4.3 Authority Check
Authority checks will be carried out as given in the respective FRSs.
4.4 Program Structure
ABAP programs are responsible for data processing within the individual dialog steps (ie. events) of an application program. This means that the program cannot be constructed as a single sequential unit, but must be divided into sections that can be assigned to the individual dialog steps. To meet this requirement, ABAP programs should have a modular structure. Each module is called a processing block. A processing block consists of a set of ABAP statements. When a program is run, effectively a series of processing blocks is called. Therefore, they should not be nested but modularized.
Each ABAP program consists of the following two parts:
4.4.1 Declaration data for global data, classes and selection screens
The first part of an ABAP program is the declaration part for global data, classes, and selection screens. This consists of:
All declaration statements for global data. Global data is visible in all internal processing blocks and should be defined using declarative statements that appear before the first processing block, in dialog modules, or in event blocks. Local data should not be declared in dialog modules or event blocks.
All selection screen definitions.
All local class definitions (CLASS DEFINITION statement). Local classes are part of ABAP Objects, the object-oriented extension of ABAP.
Declaration statements which occur in procedures (methods, subroutines, function modules) form the declaration part for local data in those processing blocks. This data is only visible within the procedure in which it is declared.
4.4.2 Container for Processing Blocks
The second part of an ABAP program contains all of the processing blocks for the program. The following types of processing blocks are allowed:
1. Dialog modules (no local data area)
2. Event blocks (no local data area)
3. Procedures (methods, subroutines and function modules with their own local data area).
Whereas dialog modules and procedures are enclosed in the ABAP keywords which define them, event blocks are introduced with event keywords and concluded implicitly by the beginning of the next processing block.
All ABAP statements (except declarative statements in the declaration part of the program) are part of a processing block. Non-declarative ABAP statements, which occur between the declaration of global data and a processing block are automatically assigned to the START-OF-SELECTION processing block.
4.4.3 Calling Processing Blocks
Processing blocks can be called from either the ABAP program or using ABAP commands which are themselves part of a processing block. Dialog modules and event blocks are called from outside the ABAP program. Procedures are called using ABAP statements in ABAP programs.
Calling event blocks is different from calling other processing blocks for the following reasons:
An event block call is triggered by an event. User actions on selection screens and lists, and the runtime environment trigger events that can be processed in ABAP programs. Define event blocks for the events that the program needs to react to (whereas a subroutine call, for example, must have a corresponding subroutine). This ensures that while an ABAP program may react to a particular event, it is not forced to do so.
4.5 Screen Flow Logic (Dialog Programs)
4.5.1 Place the AT EXIT COMMAND at the beginning of the flow logic.
Example:
PROCESS AFTER INPUT
MODULE EXIT_1170 AT EXIT-COMMAND.
MODULE PAINT_1170.
4.5.2 Use FIELD and CHAIN statements to keep fields in error open for correction.
Example:
PROCESS AFTER INPUT.
MODULE EXIT_1170 AT EXIT-COMMAND.
CHAIN.
FIELD BTCH1170-JOBNAME.
FIELD BTCH1170-USERNAME.
FIELD BTCH1170-FROM_DATE.
FIELD BTCH1170-FROM_TIME.
MODULE PAINT_1170.
ENDCHAIN.
4.6 Main Program
4.6.1 Events
The Program MUST NOT be coded without the use of Proper Coding blocks
Initializations
Top-of-page during line-selection
At Selection-Screen
At Line-Selection
At User-Command
At Pfn
Start-Of-Selection
Top-Of-Page
Get
End-Of-Page
End-Of-Selection
NOTE: The coding for each event should be logically split into forms (subroutines). That is to say, each event will comprise mostly of PERFORM statements.
5. General Coding Standards
5.1 One command per line
Each ABAP/4 command consists of a sentence ending with a period. Multiple commands can be on one line; however, as a standard start each new command on a new line. This will allow for easier deleting, commenting, and debugging.
5.2 Indented Source Code
The ABAP/4 editor has a "Pretty Printer" command to indent by 2 positions specific lines of code and add subroutine comments. Event keywords are typically not indented.
5.3 Extended Syntax Check
Extended Program Check (EPC) to be done on each object to make sure the code is Syntactically correct. There should be no Error/warning messages in the code.
5.4 Reusability and Modularity
If a block of code is executed more than once, it should be placed in a subroutine at the bottom of the code. This makes the code more readable, requires less indentation, and is easier to debug since the debugger can jump through an entire subroutine via a PF key. Also, when possible parameters should be passed to and from subroutines to make the purpose easier to understand and reduce the need for global variables. Always document the purpose of each parameter.
5.5 Text Handling
Text elements must be used to display any text messages.
5.6 Usage of System Variables
The system variables should be used wherever possible. The SY-SUBRC is to be checked after any function call, selection operation, etc.
5.7 Chaining Statements
Consecutive sentences with an identical beginning shall be combined into a chained statement.
Example:
Instead of the statements
MOVE SY-MANDT TO D00001-MANDT.
MOVE SY-LANGU TO D00001-SPRAS.
A chained statement shall be used
MOVE:
SY-MANDT TO D00001-MANDT,
SY-LANGU TO D00001-SPRAS,
SY-UNAME TO D00001-BNAME.
5.8 Common Routines
Standard sub-routines should be implemented as FUNCTION's rather than a FORM (ie. SUBROUTINE). A FUNCTION is easier to maintain and can be easily tested without a calling program. Standard SAP function modules are also available and the function library should be used to check if function modules already exist for a function that needs to be performed i.e.POPUP_TO_CONFIRM_LOSS_OF_DATA etc.
Includes can also be created for re-usable or common code e.g. common data declaration statements.
5.9 Dialog Messages
Dialogue messages are stored in table T100. Programmers shall check to see if an appropriate message exists before adding a new message. Programs shall use the message-id which corresponds to the SAP module that the program most relates to.
5.10 Function Keys
PF-keys should be programmed to execute functions where required. SAP Standard function keys should be used where appropriate. The most commonly used buttons should be displayed as pushbuttons in the application toolbar.
5.11 Enqueuing and Dequeuing Data Objects
All database objects being processed by a program, for purposes other than for display, shall be enqueued before such processing is executed. If the enqueue is unsuccessful, then a message shall be returned stating why the enqueue was unsuccessful.
Enqueue and Dequeue objects should be created via the data dictionary.
5.12 Error Handling (SY-SUBRC)
Return codes shall always be checked immediately after an event which returns a code.
Eg. Function calls, Select statements, Updates etc.
The value of SY-SUBRC is 0 when successful and generally produces a value of 4 when unsuccessful (there are a few exceptions).
Therefore, rather check SY-SUBRC with:
IF SY-SUBRC <> 0
than with
IF SY-SUBRC = 4 (which is redundant and makes the system do a double check)
Error messages displayed to the user must be clear and descriptive.
Remember to group related / dependant steps together and to Rollback all changes for steps in that group should any one of them fail, thus maintaining the integrity of the system.
Check whether an Error Log, (file), must be produced by your program and if so check on the format of the file.
If any Error Logging is done to a custom table in the database then make sure this table is maintained and monitored correctly. (Dev. Note)
Transaction SE91 provides the facility to create and utilize messages in their appropriate message class. Elaborate on the message if necessary, using the long text documentation for that message number.
5.13 General Conventions and Hints
There should be NO hard coding of values in programs easy maintainability
For amounts, use the CURRENCY command in write statements to automatically convert fields into their correct decimal format. The currency specified in the write statement is treated as a key for the table TCURX. If no entry exists for the currency specified, the system assumes two decimal places.
For quantities, use the UNIT command in write statements to automatically convert fields into their correct decimal format. The contents of the unit specified are used on table T006. If no entry exists for the unit specified, the formatting has no effect.
Use the LIKE statement as often as possible to declare DATA variables instead of an explicit TYPE declarations.
Try to use the INCLUDE statement with standard SAP structures and tables for your structures and internal tables where possible. If you use the include statement to include other program components in your code then document what those components are, what they do and how to use them.
Try to make use of standard SAP Function Modules wherever possible rather than building your own. Use the pull down functionality in transaction SE37 to find suitable standard function modules.
Make use of the SAP PATTERN tool to automatically insert the standard code for:
CALL FUNCTION
MESSAGE ID
SELECT*FROM
PERFORM
AUTHORITY-CHECK
WRITE
CASE
CALL DIALOG
The standard date format to use is DD/MM/YYYY. (Dev. Note)
The standard time format to use is HH:MM:SS.
5.14 Parameters in Sub-Routines
Naming convention for Parameters in subroutine is P_
6. Performance Standards
6.1 General Tips on Performance Tuning
6.1.1 Avoid Redundant code
Avoid leaving "dead" code in the program. Comment out variables that are not referenced and code that is not executed. To analyze the program, use the Program Analysis function in SE38 -> Utilities -> Program Analysis.
6.1.2 Subroutine Usage
For good modularization, the decision of whether or not to execute a subroutine should be made before the subroutine is called.
Example:
IF f1 NE 0.
PERFORM sub1.
ENDIF.
FORM sub1.
ENDFORM.
6.1.3 Case vs. Nested IF
When testing fields "equal to" something, one can use either the nested IF or the CASE statement. The CASE is better for two reasons. It is easier to read and after about five nested IFs the performance of the CASE is more efficient.
6.1.4 Using the MOVE Statement
When records a and b have the exact same structure, it is more efficient to MOVE a TO b than to MOVE-CORRESPONDING a TO b.
6.1.5 SELECT Queries
The performance of any ABAP program mainly depends on the ABAP Queries used in it. More optimum the queries , better the performance. Take care of the points mentioned nin the following sections while writing any ABAP queries.
6.1.5.1 Using all the keys in SELECT statement
When using the SELECT statement, study the key and always provide as much of the left-most part of the key as possible. The SELECT * command is to be avoided everywhere.
6.1.5.2 Fetching Single Record
If the entire key can be qualified, code a SELECT SINGLE not just a SELECT. If all the keys are not available, we should use SELECT UPTO 1 ROWS if we are interested only in the first record.
6.1.5.3 Avoid SELECT-ENDSELECT
Selecting data into an internal table using an array fetch versus a SELECT-ENDELECT loop will give at least a 2x performance improvement. After the data has been put into the internal data, then row-level processing can be done.
Example:
select ... from table <..>
into <itab>
where ...
loop at <itab>
<do the row-level processing here>
endloop.
6.1.5.4 Using Indexs
Use indexes wherever possible. Tune the Query so that optimum Indexing will happen.
6.1.5.5 Provide all the keys
Give as many keys as possible in the WHERE clause to optimize the database fetching. Use the Index fields in the first position to optimize performance.
6.1.5.6 Avoid INTO CORRESPONDING
Avoid using INTO CORESPONDING FIELDS of Table. Instead, explicitly mention the fields. Else, The Table Fields should be in the same sequence as the selection
6.1.5.7 SELECT statement inside LOOP
Do not write SELECT statements inside the loop. Instead, use the FOR ALL ENTRIES Command
Before using FOR ALL ENTRIES command, check that the
1. Corresponding Internal table is not empty. If the Internal table is empty, the statement will select ALL the entries in the Database
2. The Internal table is sorted by the Filed used in the Where Clause: This makes selection faster
6.1.5.8 Nested SELECT statement
Avoid Using nested SELECT statements. Instead, make use of different internal tables to fetch the data, and Use Nested LOOPS to read them.
6.1.5.9 Select Distinct
Whenever its possible avoid SELECT DISTINCT, instead select data into internal table, sort and use DELETE ADJACENT DUPLICATES
6.1.5.10 Use of OR in Where Clause
Do not use OR when selecting data from DB table using an index because The optimizer generally stops if the WHERE condition contains an OR expression.
e.g.
Instead of
SELECT * FROM spfli WHERE carrid = LH
AND (cityfrom = FRANKFURT OR
city from = NEWYORK)
Use
SELECT * FROM spfli WHERE (carrid = LH AND cityfrom = FRANKFURT)
OR (carrid = LH AND cityfrom = NEWYORK).
6.1.5.11 Order By
ORDER BY will Bypass buffer. So, performance will decrease. If you want to sort data, it is efficient to SORT them in INTERNAL TABLE rather than using ORDER BY. Only use an ORDER BY in your SELECT if the order matches the index, which should be used.
6.1.6 Using the READ statement
When reading a single record in an internal table, the READ TABLE WITH KEY is not a direct READ. The table needs to be sorted by the Key fields and the command READ TABLE WITH KEY BINARY SEARCH is to be used.
6.1.7 Hashed table
If the number of entries in the Internal Table is high then use Hashed Table with Keys to access the table.
6.1.8 Transporting
With READ or MODIFY Statements use TRANSPORTING
6.1.9 Using LDB
In order to improve performance in case of an LDB, individual tables can be excluded from selection. Under the section Table Selection in the Documentation of LDB the fields with proper description has been given those fields can be set in the application report at the time of INITIALIZATION or at the START OF SELECTION. This can enhance the performance.
6.1.10 Append Lines of
Whenever it is possible use APPEND LINES OF to append the internal Tables instead of using loop and then APPEND Statement.
6.1.11 Use WHILE
Use WHILE instead of a DO+EXIT-construction, as WHILE is easier to understand and faster to execute
6.1.12 DELETE <itab> WHERE
Use DELETE <itab> WHERE for deleting records from an internal table.
e.g.
Instead of
LOOP AT <itab> WHERE <field> = 0001
DELETE <itab>.
ENDLOOP.
Use
DELETE <itab> WHERE <field> = 0001.
6.1.13 Using WHERE clause in LOOP .ENDLOOP
Use:
Sort ITAB by NAME.
Loop at itab where name EQ SY-UNAME
Endloop.
Instead Of:
Read itab with key name = SY-UNAME.
L_tabix = sy-tabix.
Loop at itab from l_tabix.
If name eq bijoy
Endif.
Endloop. -
I have the original battery that came with the Thunderbolt. I noticed if I'm using mobile web for maybe over 20 minutes or so, I can feel the battery heating up. Is anyone else experiencing this with the original battery? Is this "normal"? I don't notice it heating up when I just text or use the phone for voice calls. It's past the 14d period when I can return the phone. My laptop was doing the same thing (heating up), until finally it "burned out" the inside and has had to be repaired several times. I'd HATE for the same thing tohappen to my Thunderbolt, especially since I have 2 years with it. (Footnote: I did not purchase the extended warranty.) Help!!!
Download from the market "Battery Monitor" application and it will show you much more information about battery including its temperature. Normailly working battery temperature (not during charging) range is from 80F (27C) and should not exceed 105F (40C). If your battery is getting hotter than 105F during normal operation, you are risking of damaging not just a battery but also internal components of the phone.
-
I want to use the Apple TV to create an interactive white board type setting in the classroom. I appreciate the help.
My first reply was probably a bit vague but it's not clear exactly what you're planning to do.
Anyhow first off, remember this is simply a user to user forum and is not an Apple staffed technical advice area so no one here can accept any responsibility for the implementation you attempt.
If you intend to do anything that could potentially compromise patient confidentiality you must get appropriate advice from suitable agencies including your IT dept and probably Apple itself. Depending which country you are in you will be subject to local healthcare laws aimed at protecting patient confidentiality.
As users we know next to nothing about AppleTV under the hood security.
AppleTV runs a version of iOS just like iPhones and iPads.
There is no antivirus/firewall software for iOS as it's already pretty locked down.
That does not mean it is 100% secure as nothing is, and all these devices can potentially be hacked.
AppleTV itself does not store any content permanently, losing data when it's unplugged, so that is probably not an issue unless someone was going to attempt a forensic style data rescue from the internal components.
If your IT dept allows iPhones or iPads on the network then in principle it's the same, and in many ways less of an issue as it doesn't support 3rd party apps, only a small selection of features from Apple and selected partners.
I assume for your whiteboard plan this would entail using a touch screen like an iPad for mirroring. Be aware that fullscreen mirroring will send a 4:3 image to the display as the iPad screen is 4:3 not 16:9 (widescreen).
You need to work with your IT dept to assess the feasibility of what you want to do - unless you need internet access, to me it would seem a standalone local network without internet connectivity might remove some concerns about devices connecting to the main hospital network. Maybe their concern is simply wifi and possible interecption of data sent to the AppleTV - this would likely be a proprietary screen sharing format for Airplay but it could still potentially be intercepted on wifi though I can't really see why anyone would want to as the data would probably be pretty useless to them unless this was a specific attempt to capture Airplay streams and people knew what they were doing and had compromised your wifi security.
Good luck.
AC -
I can no longer use 3D commands in Photoshop CS6 Extended
I have Photoshop CS6 Extended (Ver 13.0.1x64). My desktop is Windows 7 64 Home premium; and Video card is: AMD Radeon HD 5570. The drivers and operating system is updated.
I have been using simple 3D functions like "New 3D extrusion from..." from time to time without any problems until recently. For unknown reasons now when I try to invoke any 3D command, I get the following message: " Could not complete the "New 3D extrusion from selected layer command because of a program error." This ,message gets repeated for any 3D command.
I checked out 3D functionality in Photoshop CS6 32 bit; and Photoshop CS5.5 Extended. Same problem. However, I can access and use all 3D functions in Illustrator CS6. Clearly, therefore, the video card is not the problem. It looks like one of the recent software updates from Adobe must have caused this problem.
Reproduced below are details of my system:
Please help!
Priyaranjan Desai
Adobe Photoshop Version: 13.0.1 (13.0.1.3 20131024.r.34 2013/10/24:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:7, Stepping:10 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1
Physical processor count: 4
Processor speed: 2660 MHz
Built-in memory: 8191 MB
Free memory: 2569 MB
Memory available to Photoshop: 7234 MB
Memory used by Photoshop: 69 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Normal
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: ATI Technologies Inc.
Video Card Renderer: AMD Radeon HD 5570
Display: 2
Display Bounds:= top: 0, left: 2560, bottom: 1200, right: 4480
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 1440, right: 2560
Video Card Number: 1
Video Card: AMD Radeon HD 5570
OpenCL Version:
Driver Version: 14.100.0.0
Driver Date: 20140417000000.000000-000
Video Card Driver: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.d ll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Video Mode: 2560 x 1440 x 4294967296 colors
Video Card Caption: AMD Radeon HD 5570
Video Card Memory: 1024 MB
Video Rect Texture Size: 16384
Serial number: 92278705978377249761
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Piyush\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
C:\, 686.9G, 231.5G free
L:\, 2.73T, 2.18T free
S:\, 2.73T, 904.6G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
A3DLIBS.dll A3DLIB Dynamic Link Library 9.2.0.112
ACE.dll ACE 2012/06/05-15:16:32 66.507768 66.507768
adbeape.dll Adobe APE 2012/01/25-10:04:55 66.1025012 66.1025012
AdobeLinguistic.dll Adobe Linguisitc Library 6.0.0
AdobeOwl.dll Adobe Owl 2012/06/26-12:17:19 4.0.95 66.510504
AdobePDFL.dll PDFL 2011/12/12-16:12:37 66.419471 66.419471
AdobePIP.dll Adobe Product Improvement Program 6.0.0.1654
AdobeXMP.dll Adobe XMP Core 2012/02/06-14:56:27 66.145661 66.145661
AdobeXMPFiles.dll Adobe XMP Files 2012/02/06-14:56:27 66.145661 66.145661
AdobeXMPScript.dll Adobe XMP Script 2012/02/06-14:56:27 66.145661 66.145661
adobe_caps.dll Adobe CAPS 6,0,29,0
AGM.dll AGM 2012/06/05-15:16:32 66.507768 66.507768
ahclient.dll AdobeHelp Dynamic Link Library 1,7,0,56
aif_core.dll AIF 3.0 62.490293
aif_ocl.dll AIF 3.0 62.490293
aif_ogl.dll AIF 3.0 62.490293
amtlib.dll AMTLib (64 Bit) 6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00) 1.000000
ARE.dll ARE 2012/06/05-15:16:32 66.507768 66.507768
AXE8SharedExpat.dll AXE8SharedExpat 2011/12/16-15:10:49 66.26830 66.26830
AXEDOMCore.dll AXEDOMCore 2011/12/16-15:10:49 66.26830 66.26830
Bib.dll BIB 2012/06/05-15:16:32 66.507768 66.507768
BIBUtils.dll BIBUtils 2012/06/05-15:16:32 66.507768 66.507768
boost_date_time.dll DVA Product 6.0.0
boost_signals.dll DVA Product 6.0.0
boost_system.dll DVA Product 6.0.0
boost_threads.dll DVA Product 6.0.0
cg.dll NVIDIA Cg Runtime 3.0.00007
cgGL.dll NVIDIA Cg Runtime 3.0.00007
CIT.dll Adobe CIT 2.0.5.19287 2.0.5.19287
CoolType.dll CoolType 2012/06/05-15:16:32 66.507768 66.507768
data_flow.dll AIF 3.0 62.490293
dvaaudiodevice.dll DVA Product 6.0.0
dvacore.dll DVA Product 6.0.0
dvamarshal.dll DVA Product 6.0.0
dvamediatypes.dll DVA Product 6.0.0
dvaplayer.dll DVA Product 6.0.0
dvatransport.dll DVA Product 6.0.0
dvaunittesting.dll DVA Product 6.0.0
dynamiclink.dll DVA Product 6.0.0
ExtendScript.dll ExtendScript 2011/12/14-15:08:46 66.490082 66.490082
FileInfo.dll Adobe XMP FileInfo 2012/01/17-15:11:19 66.145433 66.145433
filter_graph.dll AIF 3.0 62.490293
hydra_filters.dll AIF 3.0 62.490293
icucnv40.dll International Components for Unicode 2011/11/15-16:30:22 Build gtlib_3.0.16615
icudt40.dll International Components for Unicode 2011/11/15-16:30:22 Build gtlib_3.0.16615
icudt42.dll International Components for Unicode 4, 2, 0, 0
icuin42.dll International Components for Unicode 4, 2, 0, 0
icuuc42.dll International Components for Unicode 4, 2, 0, 0
image_compiler.dll AIF 3.0 62.490293
image_flow.dll AIF 3.0 62.490293
image_runtime.dll AIF 3.0 62.490293
JP2KLib.dll JP2KLib 2011/12/12-16:12:37 66.236923 66.236923
libifcoremd.dll Intel(r) Visual Fortran Compiler 10.0 (Update A)
libmmd.dll Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler 10.0
LogSession.dll LogSession 2.1.2.1640
mediacoreif.dll DVA Product 6.0.0
MPS.dll MPS 2012/02/03-10:33:13 66.495174 66.495174
msvcm80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcm90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
msvcp100.dll Microsoft® Visual Studio® 2010 10.00.40219.1
msvcp80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcp90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
msvcr100.dll Microsoft® Visual Studio® 2010 10.00.40219.1
msvcr80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcr90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
ONCore7.dll ONCore 7.0.0.0
ONCore8.dll ONCore 7.0.0.0
ONCoreFoundation7.dll ONCoreFoundation7 7, 0, 0, 0
ONCoreFoundation8.dll ONCoreFoundation7 7, 0, 0, 0
ONDocument7.dll ONDocument 7.0.0.0
ONDocument8.dll ONDocument 7.0.0.0
onOneToolbox2.dll onOne Toolbox2 Dynamic Link Library 2.2.0
OnOneWidgets.dll OnOneWidgets dll 2.5
ONProxySupport7.dll ONProxySupport 1.0.0.0
ONProxySupport8.dll ONProxySupport 1.0.0.0
pdfsettings.dll Adobe PDFSettings 1.04
Photoshop.dll Adobe Photoshop CS6 CS6
Plugin.dll Adobe Photoshop CS6 CS6
PlugPlug.dll Adobe(R) CSXS PlugPlug Standard Dll (64 bit) 3.0.0.383
PSArt.dll Adobe Photoshop CS6 CS6
PSViews.dll Adobe Photoshop CS6 CS6
SCCore.dll ScCore 2011/12/14-15:08:46 66.490082 66.490082
ScriptUIFlex.dll ScriptUIFlex 2011/12/14-15:08:46 66.490082 66.490082
tbb.dll Intel(R) Threading Building Blocks for Windows 3, 0, 2010, 0406
tbbmalloc.dll Intel(R) Threading Building Blocks for Windows 3, 0, 2010, 0406
TfFontMgr.dll FontMgr 9.3.0.113
TfKernel.dll Kernel 9.3.0.113
TFKGEOM.dll Kernel Geom 9.3.0.113
TFUGEOM.dll Adobe, UGeom© 9.3.0.113
updaternotifications.dll Adobe Updater Notifications Library 6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME) 6.0.0.24
WRServices.dll WRServices Friday January 27 2012 13:22:12 Build 0.17112 0.17112
wu3d.dll U3D Writer 9.3.0.113
Required plug-ins:
3D Studio 13.0.1 (13.0.1.3 x001)
Accented Edges 13.0
Adaptive Wide Angle 13.0
ADM 3.11x01
Angled Strokes 13.0
Average 13.0.1 (13.0.1.3 x001)
Bas Relief 13.0
BMP 13.0
Chalk & Charcoal 13.0
Charcoal 13.0
Chrome 13.0
Cineon 13.0.1 (13.0.1.3 x001)
Clouds 13.0.1 (13.0.1.3 x001)
Collada 13.0.1 (13.0.1.3 x001)
Color Halftone 13.0
Colored Pencil 13.0
CompuServe GIF 13.0
Conté Crayon 13.0
Craquelure 13.0
Crop and Straighten Photos 13.0.1 (13.0.1.3 x001)
Crop and Straighten Photos Filter 13.0
Crosshatch 13.0
Crystallize 13.0
Cutout 13.0
Dark Strokes 13.0
De-Interlace 13.0
Dicom 13.0
Difference Clouds 13.0.1 (13.0.1.3 x001)
Diffuse Glow 13.0
Displace 13.0
Dry Brush 13.0
Eazel Acquire 13.0.1 (13.0.1.3 x001)
Embed Watermark 4.0
Entropy 13.0.1 (13.0.1.3 x001)
Extrude 13.0
FastCore Routines 13.0.1 (13.0.1.3 x001)
Fibers 13.0
Film Grain 13.0
Filter Gallery 13.0
Flash 3D 13.0.1 (13.0.1.3 x001)
Fresco 13.0
Glass 13.0
Glowing Edges 13.0
Google Earth 4 13.0.1 (13.0.1.3 x001)
Grain 13.0
Graphic Pen 13.0
Halftone Pattern 13.0
HDRMergeUI 13.0
Histogram 2.1.3
HistogramCurves 2.1.3
IFF Format 13.0
Ink Outlines 13.0
JPEG 2000 13.0
Kurtosis 13.0.1 (13.0.1.3 x001)
Lens Blur 13.0
Lens Correction 13.0
Lens Flare 13.0
Liquify 13.0
Matlab Operation 13.0.1 (13.0.1.3 x001)
Maximum 13.0.1 (13.0.1.3 x001)
Mean 13.0.1 (13.0.1.3 x001)
Measurement Core 13.0.1 (13.0.1.3 x001)
Median 13.0.1 (13.0.1.3 x001)
Mezzotint 13.0
Minimum 13.0.1 (13.0.1.3 x001)
MMXCore Routines 13.0.1 (13.0.1.3 x001)
Mosaic Tiles 13.0
Multiprocessor Support 13.0.1 (13.0.1.3 x001)
Neon Glow 13.0
Note Paper 13.0
NTSC Colors 13.0.1 (13.0.1.3 x001)
Ocean Ripple 13.0
Oil Paint 13.0
OpenEXR 13.0
Paint Daubs 13.0
Palette Knife 13.0
Patchwork 13.0
Paths to Illustrator 13.0
PCX 13.0.1 (13.0.1.3 x001)
Photocopy 13.0
PhotoKit 1, 2, 11, 0
PhotoKit Capture Sharpener 1, 2, 11, 0
PhotoKit Capture Sharpener Expert 1, 2, 11, 0
PhotoKit Color 2 2.1.3
PhotoKit Creative Sharpener 1, 2, 11, 0
PhotoKit Output Sharpener 1, 2, 11, 0
PhotoKit Preview Helper 2.1.3
Photoshop 3D Engine 13.0.1 (13.0.1.3 x001)
Picture Package Filter 13.0.1 (13.0.1.3 x001)
Pinch 13.0
Pixar 13.0.1 (13.0.1.3 x001)
PixelGenius Toolbox 2.1.3
Plaster 13.0
Plastic Wrap 13.0
PNG 13.0
Pointillize 13.0
Polar Coordinates 13.0
Portable Bit Map 13.0.1 (13.0.1.3 x001)
Poster Edges 13.0
Radial Blur 13.0
Radiance 13.0.1 (13.0.1.3 x001)
Range 13.0.1 (13.0.1.3 x001)
Read Watermark 4.0
Reticulation 13.0
Ripple 13.0
Rough Pastels 13.0
Save for Web 13.0
ScriptingSupport 13.0.1
Shear 13.0
Skewness 13.0.1 (13.0.1.3 x001)
Smart Blur 13.0
Smudge Stick 13.0
Solarize 13.0.1 (13.0.1.3 x001)
Spatter 13.0
Spherize 13.0
Sponge 13.0
Sprayed Strokes 13.0
Stained Glass 13.0
Stamp 13.0
Standard Deviation 13.0.1 (13.0.1.3 x001)
Sumi-e 13.0
Summation 13.0.1 (13.0.1.3 x001)
Targa 13.0
Texturizer 13.0
Tiles 13.0
Topaz Star Effects 10.0
Torn Edges 13.0
Twirl 13.0
U3D 13.0.1 (13.0.1.3 x001)
Underpainting 13.0
Vanishing Point 13.0
Variance 13.0.1 (13.0.1.3 x001)
Variations 13.0.1 (13.0.1.3 x001)
Water Paper 13.0
Watercolor 13.0
Wave 13.0
Wavefront|OBJ 13.0.1 (13.0.1.3 x001)
WIA Support 13.0.1 (13.0.1.3 x001)
Wind 13.0
Wireless Bitmap 13.0.1 (13.0.1.3 x001)
ZigZag 13.0
Optional and third party plug-ins:
Alias PIX 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
Alien Skin Autolayer 3 3.0.0 20463 2013-05-30 12:54
Alien Skin Blow Up 3 3.0.0
Alien Skin Exposure 5 Autolayer 5.0.0
Alien Skin Exposure 6 Autolayer 6.0.0
Alien Skin Eye Candy 7 Autolayer 7.0.0
Alien Skin Snap Art 4 Autolayer 4.0.0
Animal Fur 6.1.1
BackgroundFilter NO VERSION
Backlight 6.1.1
Bevel 6.1.1
Blow Up 3.0.0
Bokeh 2.0.1
Brick Wall 6.1.1
Brushed Metal 6.1.1
Camera Raw 8.6
Camera Raw Filter 8.6
Chrome 6.1.1
Color Efex Pro 4 4,05
Color Efex Pro 4 4,05
Corona 6.1.1
Dfine 2.0 NO VERSION
Diamond Plate 6.1.1
Drip 6.1.1
DxO FilmPack 3 NO VERSION
ElectricImage 13.0
Exposure 5 5.0.0
Exposure 6 6.0.0
Extrude 6.1.1
Eye Candy 7 7.0.0
FineStructuresFilter NO VERSION
Fire 6.1.1
Fisheye-Hemi 1 (Circle) [x64] v1.2.5 1.2.5.0
Fisheye-Hemi 1 (Circle) [x64] v1.2.5 1.2.5.0
Fisheye-Hemi 2 (Full Frame) [x64] v1.2.5 1.2.5.0
Fisheye-Hemi 2 (Full Frame) [x64] v1.2.5 1.2.5.0
Fisheye-Hemi 3 (Cropped) [x64] v1.2.5 1.2.5.0
Fisheye-Hemi 3 (Cropped) [x64] v1.2.5 1.2.5.0
Glass 6.1.1
Gradient Glow 6.1.1
HDR Efex Pro 2 2,03
HotPixelsFilter NO VERSION
HSB/HSL 13.0
Icicles 6.1.1
Imagenomic Plug-in Console 1, 2, 0, 0
Lighting Effects Classic 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
Marble 6.1.1
Merge to HDR Efex Pro 2 2,03
Motion Trail 6.1.1
Nik Selective Tool 2.1.4.20903
Noiseware 2.3.0.9
Perfect Batch 8 8.5.1
Perfect BW 8 8.5.1
Perfect BW 8 Filter 8.5.1
Perfect BW 8 Smart Filter 8.5.1
Perfect Effects 4 4.0
Perfect Effects 4 Filter 4.0
Perfect Effects 4 Smart Filter 4.0
Perfect Effects 8 8.5.1
Perfect Effects 8 Filter 8.5.1
Perfect Effects 8 Smart Filter 8.5.1
Perfect Enhance 8 8.5.1
Perfect Enhance 8 Filter 8.5.1
Perfect Enhance 8 Smart Filter 8.5.1
Perfect Mask 8 8.5.1
Perfect Mask 8 Filter 8.5.1
Perfect Mask 8 Smart Filter 8.5.1
Perfect Portrait 8 8.5.1
Perfect Portrait 8 Filter 8.5.1
Perfect Portrait 8 Smart Filter 8.5.1
Perfect Resize 8 8.5.1
Perfect Resize 8 Engine Automation 8.5.1
Perfect Resize 8 Engine Filter 8.5.1
Perfect Resize 8 Filter 8.5.1
Perspective Shadow 6.1.1
PhotoFrame 4.6 Free 4.6.5
PhotoFrame 4.6 Free Batch 4.6.5
PhotoFrame 4.6 Free Hidden 4.6.5
Plug-in on new layer 2, 0, 4, 0
Portrait Professional 1, 4, 1, 0
Portrait+ 1.5.1.149
Portraiture 2.3.0.8
RealGrain 1.1.0.3
Reptile Skin 6.1.1
Ripples 6.1.1
Rust 6.1.1
SGI RGB 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
ShadowsFilter NO VERSION
Sharpener Pro 3.0: (1) RAW Presharpener 3.0.10.20903
Sharpener Pro 3.0: (2) Output Sharpener 3.0.10.20903
Silver Efex Pro 2 2,006
Silver Efex Pro 2 2,006
SkinFilter NO VERSION
SkyFilter NO VERSION
Smoke 6.1.1
Snap Art 4 4.0.0
Snow Drift 6.1.1
SoftImage 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
Squint 6.1.1
Stone Wall 6.1.1
StrongNoiseFilter NO VERSION
Super Star 6.1.1
Swirl 6.1.1
Texture Noise 6.1.1
Topaz Adjust 4 10.0
Topaz Adjust 5 10.0
Topaz BW Effects 10.0
Topaz Clarity 10.0
Topaz Clean 3 10.0
Topaz DeJpeg 4 10.0
Topaz DeNoise 5 10.0
Topaz Detail 2 10.0
Topaz Detail 3 10.0
Topaz InFocus 10.0
Topaz Lens Effects 10.0
Topaz photoFXlab 10.0
Topaz ReMask 3 10.0
Topaz Simplify 3 10.0
Topaz Simplify 4 10.0
TopazRemaskAutomate NO VERSION
Viveza 2 2.0.9.20903
Water Drops 6.1.1
Wavefront RLA 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
Weave 6.1.1
Wood 6.1.1
Plug-ins that failed to load: NONE
Flash:
Paper Texture
onOne
Gallery Wrapper
Mini Bridge
GuideGuide
Kuler
Installed TWAIN devices: NONETo use "dictation" as it is called, there are two requirements:
1. Siri must be turned on (Settings > General > Siri)
2. You must be connected to the internet. -
Bonjour, je recherche une version d'adobe media encoder CC mais en 32 bit, j'ai bien la version 64 bit mais il n'y a pas moyen de la lancer comme d'ailleurs les version 64bit de indesign/illustrator/lightroom... y a que photoshop qui fonctionne en 64bit chez moi!
J'ai cherché dans la page téléchargement d'adobe mais je ne trouve que la version 64bit. Donc si quelqu'un a un lien ou une solution je suis preneur.
merci a vous, bon aprém.merci de votre réponse rapide, le contenu de l'info-système de photoshop CC x64 :
Version Adobe Photoshop : 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00) x64
Système d'exploitation : Windows 7 64 bits
Version : 6.1 Service Pack 1
Architecture système : UC Intel Famille :6, modèle :10, niveau :7 avec MMX, SSE Entier, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Nombre de processeurs physiques : 4
Nombre de processeurs logiques : 8
Vitesse du processeur : 3392 MHz
Mémoire intégrée : 8087 Mo
Mémoire libre : 4116 Mo
Mémoire disponible pour Photoshop : 7074 Mo
Mémoire utilisée par Photoshop : 60 %
Taille de la mosaïque d'images : 1024K
Niveaux de mémoire cache de l'image : 4
Aperçu de la police : Moyenne
Compositeur de texte : Latin
Affichage : 1
Limites d'affichage : haut = 0, gauche = 0, bas = 1080, droite = 1920
Affichage : 2
Limites d'affichage : haut = 48, gauche = 1920, bas = 948, droite = 3360
Affichage : 3
Limites d'affichage : haut = 180, gauche = 3360, bas = 948, droite = 4720
Dessin OpenGL : Activé.
Anciens GPU OpenGL autorisés : Non détectés.
Mode de dessin OpenGL : Avancé
Mode OpenGL normal autorisé : Vrai.
Mode OpenGL avancé autorisé : Vrai.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGPUs=2
gpu[0].OGLVersion="3.0"
gpu[0].MemoryMB=1024
gpu[0].RectTextureSize=16384
gpu[0].Renderer="GeForce GTX 555/PCIe/SSE2"
gpu[0].RendererID=4614
gpu[0].Vendor="NVIDIA Corporation"
gpu[0].VendorID=4318
gpu[0].HasNPOTSupport=1
gpu[0].DriverVersion="9.18.13.3788"
gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
gpu[0].DriverDate="20140519000000.000000-000"
gpu[0].CompileProgramGLSL=1
gpu[0].TestFrameBuffer=1
gpu[0].OCLPresent=1
gpu[0].OCLVersion="1.1"
gpu[0].CUDASupported=1
gpu[0].CUDAVersion="6.0.1"
gpu[0].OCLBandwidth=7.46599e+010
gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
gpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
gpu[1].OGLVersion="3.0"
gpu[1].MemoryMB=2108
gpu[1].RectTextureSize=16384
gpu[1].Renderer="GeForce GTX 555/PCIe/SSE2"
gpu[1].RendererID=258
gpu[1].Vendor="NVIDIA Corporation"
gpu[1].VendorID=32902
gpu[1].HasNPOTSupport=1
gpu[1].DriverVersion="9.17.10.3347"
gpu[1].Driver="igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32"
gpu[1].DriverDate="20140129000000.000000-000"
gpu[1].CompileProgramGLSL=1
gpu[1].TestFrameBuffer=1
gpu[1].OCLPresent=1
gpu[1].OCLVersion="1.1"
gpu[1].CUDASupported=1
gpu[1].CUDAVersion="6.0.1"
gpu[1].OCLBandwidth=7.47211e+010
gpu[1].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[1].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[1].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[1].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[1].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[1].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[1].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[1].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[1].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[1].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[1].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[1].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[1].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[1].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[1].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[1].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[1].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[1].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
gpu[1].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
gpu[1].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
gpu[1].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
Type de licence : Abonnement
Numéro de série : 90970196649322984791
Dossier de l'application : C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\
Chemin des fichiers temporaires : C:\Users\mickael\AppData\Local\Temp\
Le disque de travail de Photoshop comporte l'E/S asynchrone activé.
Volume(s) de travail :
C:\, 930,3 Go, 321,0 Go libres
Dossier des modules externes obligatoires : C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Required\Plug-Ins\
Dossier principal des modules externes : C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Plug-ins\
Composants installés :
ACE.dll ACE 2013/10/29-11:47:16 79.548223 79.548223
adbeape.dll Adobe APE 2013/02/04-09:52:32 0.1160850 0.1160850
AdobeLinguistic.dll Adobe Linguisitc Library 7.0.0
AdobeOwl.dll Adobe Owl 2013/10/25-12:15:59 5.0.24 79.547804
AdobePDFL.dll PDFL 2013/10/29-11:47:16 79.508720 79.508720
AdobePIP.dll Adobe Product Improvement Program 7.0.0.1786
AdobeXMP.dll Adobe XMP Core 2013/10/29-11:47:16 79.154911 79.154911
AdobeXMPFiles.dll Adobe XMP Files 2013/10/29-11:47:16 79.154911 79.154911
AdobeXMPScript.dll Adobe XMP Script 2013/10/29-11:47:16 79.154911 79.154911
adobe_caps.dll Adobe CAPS 7,0,0,21
AGM.dll AGM 2013/10/29-11:47:16 79.548223 79.548223
ahclient.dll AdobeHelp Dynamic Link Library 1,8,0,31
aif_core.dll AIF 5.0 79.534508
aif_ocl.dll AIF 5.0 79.534508
aif_ogl.dll AIF 5.0 79.534508
amtlib.dll AMTLib (64 Bit) 7.0.0.249 BuildVersion: 7.0; BuildDate: Thu Nov 14 2013 15:55:50) 1.000000
ARE.dll ARE 2013/10/29-11:47:16 79.548223 79.548223
AXE8SharedExpat.dll AXE8SharedExpat 2011/12/16-15:10:49 66.26830 66.26830
AXEDOMCore.dll AXEDOMCore 2011/12/16-15:10:49 66.26830 66.26830
Bib.dll BIB 2013/10/29-11:47:16 79.548223 79.548223
BIBUtils.dll BIBUtils 2013/10/29-11:47:16 79.548223 79.548223
boost_date_time.dll DVA Product 7.0.0
boost_signals.dll DVA Product 7.0.0
boost_system.dll DVA Product 7.0.0
boost_threads.dll DVA Product 7.0.0
cg.dll NVIDIA Cg Runtime 3.0.00007
cgGL.dll NVIDIA Cg Runtime 3.0.00007
CIT.dll Adobe CIT 2.1.6.30929 2.1.6.30929
CITThreading.dll Adobe CITThreading 2.1.6.30929 2.1.6.30929
CoolType.dll CoolType 2013/10/29-11:47:16 79.548223 79.548223
dvaaudiodevice.dll DVA Product 7.0.0
dvacore.dll DVA Product 7.0.0
dvamarshal.dll DVA Product 7.0.0
dvamediatypes.dll DVA Product 7.0.0
dvaplayer.dll DVA Product 7.0.0
dvatransport.dll DVA Product 7.0.0
dvaunittesting.dll DVA Product 7.0.0
dynamiclink.dll DVA Product 7.0.0
ExtendScript.dll ExtendScript 2013/10/30-13:12:12 79.546835 79.546835
FileInfo.dll Adobe XMP FileInfo 2013/10/25-03:51:33 79.154511 79.154511
filter_graph.dll AIF 5.0 79.534508
icucnv40.dll International Components for Unicode 2011/11/15-16:30:22 Build gtlib_3.0.16615
icudt40.dll International Components for Unicode 2011/11/15-16:30:22 Build gtlib_3.0.16615
imslib.dll IMSLib DLL 7.0.0.145
JP2KLib.dll JP2KLib 2013/10/29-11:47:16 79.248139 79.248139
libifcoremd.dll Intel(r) Visual Fortran Compiler 10.0 (Update A)
libiomp5md.dll Intel(R) OMP Runtime Library 5.0
libmmd.dll Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler 12.0
LogSession.dll LogSession 2.1.2.1785
mediacoreif.dll DVA Product 7.0.0
MPS.dll MPS 2013/10/29-11:47:16 79.535029 79.535029
msvcm80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcm90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
msvcp100.dll Microsoft® Visual Studio® 2010 10.00.40219.1
msvcp80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcp90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
msvcr100.dll Microsoft® Visual Studio® 2010 10.00.40219.1
msvcr80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcr90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
PatchMatch.dll PatchMatch 2013/10/29-11:47:16 79.542390 79.542390
pdfsettings.dll Adobe PDFSettings 1.04
Photoshop.dll Adobe Photoshop CC CC
Plugin.dll Adobe Photoshop CC CC
PlugPlugOwl.dll Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit) 4.2.0.36
PSArt.dll Adobe Photoshop CC CC
PSViews.dll Adobe Photoshop CC CC
SCCore.dll ScCore 2013/10/30-13:12:12 79.546835 79.546835
ScriptUIFlex.dll ScriptUIFlex 2013/10/30-13:12:12 79.546835 79.546835
svml_dispmd.dll Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler 12.0
tbb.dll Intel(R) Threading Building Blocks for Windows 4, 1, 2012, 1003
tbbmalloc.dll Intel(R) Threading Building Blocks for Windows 4, 1, 2012, 1003
updaternotifications.dll Adobe Updater Notifications Library 7.0.1.102 (BuildVersion: 1.0; BuildDate: BUILDDATETIME) 7.0.1.102
WRServices.dll WRServices Mon Feb 25 2013 16:09:10 Build 0.19078 0.19078
Modules externes obligatoires :
3D Studio 14.2.1 (14.2.1 x001)
Aérographe 14.2.1
Aplatissement 14.2.1 (14.2.1 x001)
Aquarelle 14.2.1
Asymétrie 14.2.1 (14.2.1 x001)
Barbouillage 14.2.1
Bas-relief 14.2.1
BMP 14.2.1
Camera Raw 8.4.1
Carrelage 14.2.1
Chrome 14.2.1
Cineon 14.2.1 (14.2.1 x001)
Cisaillement 14.2.1
Collada 14.2.1 (14.2.1 x001)
CompuServe GIF 14.2.1
Contour accentué 14.2.1
Contour déchiré 14.2.1
Contour encré 14.2.1
Contour lumineux 14.2.1
Contour postérisé 14.2.1
Contraction 14.2.1
Coordonnées polaires 14.2.1
Correction de l'objectif 14.2.1
Couleurs NTSC 14.2.1 (14.2.1 x001)
Couteau à palette 14.2.1
Craie/Fusain 14.2.1
Craquelure 14.2.1
Crayon Conté 14.2.1
Crayon de couleur 14.2.1
Cristallisation 14.2.1
Croisillons 14.2.1
Découpage 14.2.1
Demi-teintes couleur 14.2.1
Désentrelacement 14.2.1
Diagonales 14.2.1
Dicom 14.2.1
Dispersion 14.2.1
Eazel Acquire 14.2.1 (14.2.1 x001)
Ecart type 14.2.1 (14.2.1 x001)
Effet mosaïque 14.2.1
Effet pointilliste 14.2.1
Emballage plastique 14.2.1
Enregistrer pour le Web 14.2.1
Entropie 14.2.1 (14.2.1 x001)
Eponge 14.2.1
Etalement 14.2.1
Extension WIA 14.2.1 (14.2.1 x001)
Extrusion 14.2.1
Fibres 14.2.1
Filtre Camera Raw 8.4.1
Filtre Collection d'images 14.2.1 (14.2.1 x001)
Filtre Rogner et désincliner les photos 14.2.1
Flash 3D 14.2.1 (14.2.1 x001)
Flou de l'objectif 14.2.1
Flou optimisé 14.2.1
Flou radial 14.2.1
Fluidité 14.2.1
Format IFF 14.2.1
Fresque 14.2.1
Fusain 14.2.1
Galerie de filtres 14.2.1
Google Earth 4 14.2.1 (14.2.1 x001)
Grain 14.2.1
Grain photo 14.2.1
Grand-angle adaptatif 14.2.1
Halo 14.2.1
HDRMergeUI 14.2.1
Insertion filigrane 4.0
JPEG 2000 14.2.1
Lecture filigrane 4.0
Lueur diffuse 14.2.1
Matlab Operation 14.2.1 (14.2.1 x001)
Maximum 14.2.1 (14.2.1 x001)
Médiane 14.2.1 (14.2.1 x001)
Mezzo-tinto 14.2.1
Minimum 14.2.1 (14.2.1 x001)
Moteur 3D Photoshop 14.2.1 (14.2.1 x001)
Moyenne 14.2.1 (14.2.1 x001)
Moyenne 14.2.1 (14.2.1 x001)
Multiprocesseur 14.2.1 (14.2.1 x001)
Néon 14.2.1
Noir/Blanc 14.2.1
Noyau de mesures 14.2.1 (14.2.1 x001)
Nuages 14.2.1 (14.2.1 x001)
Nuages par différence 14.2.1 (14.2.1 x001)
Océan 14.2.1
Onde 14.2.1
Ondulation 14.2.1
OpenEXR 14.2.1
Papier gaufré 14.2.1
Papier humide 14.2.1
Pastels 14.2.1
Patchwork 14.2.1
PCX 14.2.1 (14.2.1 x001)
Peinture à l'huile 14.2.1
Photocopie 14.2.1
Photoshop Touch 14.0
Pinceau à sec 14.2.1
Pixar 14.2.1 (14.2.1 x001)
Placage de texture 14.2.1
Plâtre 14.2.1
Plume calligraphique 14.2.1
PNG 14.2.1
Point de fuite 14.2.1
Pointillisme 14.2.1
Portable Bit Map 14.2.1 (14.2.1 x001)
Portée 14.2.1 (14.2.1 x001)
Radiance 14.2.1 (14.2.1 x001)
Réduction du tremblement 14.2.1
Réticulation 14.2.1
Rogner et désincliner les photos 14.2.1 (14.2.1 x001)
Routines FastCore 14.2.1 (14.2.1 x001)
Routines MMXCore 14.2.1 (14.2.1 x001)
Solarisation 14.2.1 (14.2.1 x001)
Sommation 14.2.1 (14.2.1 x001)
Soufflerie 14.2.1
Sous-couche 14.2.1
Sphérisation 14.2.1
STL 14.2.1 (14.2.1 x001)
Sumi-e 14.2.1
Support de script 14.2.1
Tampon 14.2.1
Targa 14.2.1
Tourbillon 14.2.1
Tracés vers Illustrator 14.2.1
Trame de demi-teintes 14.2.1
Variance 14.2.1 (14.2.1 x001)
Variantes 14.2.1 (14.2.1 x001)
Verre 14.2.1
Vitrail 14.2.1
Wavefront|OBJ 14.2.1 (14.2.1 x001)
Wireless Bitmap 14.2.1 (14.2.1 x001)
Zigzag 14.2.1
Dossier des modules externes tiers et facultatifs :
PSHostAdapter NO VERSION
Modules externes dont le chargement a échoué : AUCUN
Flash :
Ink
Mini Bridge
Prisma
Adobe Exchange
Modules TWAIN installés : AUCUN
Maybe you are looking for
-
Can't print .indd booklet to PDF; opens print utility instead of Acrobat
Thanks in advance for any help you can lend. I have a 16 page .indd document that I'm trying to export via "print booklet", using Adobe PDF 9.0 as my printer. Every time I try to print as a PDF, it goes through the process of compiling the images, lo
-
i have a time/date feild in Access database,,but when i make a select statement of the time, it gives me a strange date with the time : 1899-12-30 15:16:19 1899-12-30 15:17:19 1899-12-30 15:18:19 1899-12-30 15:19:19 1899-12-30 15:20:19 1899-12-30 15:
-
What is needed in a Mac Pro to start developing APPs?
I am looking for information on what Mac Pro (processor speed, memory, and storage capacity) is needed to start developing APPs. In addition, I would like my Mac Pro be viable for the next three years as I learn how to use the system to build APPs a
-
Creating an Hyperion Planning connection in Financial Reporting
We've got a lot of FM and Essbase reports, but now I'd like to connect to Planning so that I can display cell text in a report but I just can't get the connection setup from Workspace. Two things: 1. There's no button to pick my Application as with o
-
Oracle8i and 9i with JDeveloper. Use/Config Question?
We presently have an OracleLite 8i database deployed on an NT and XP mobile Platform using Oracle Forms 6.0. Can we copy the Oracle lite schema into a development environment(project/connection) in JDeveloper and Build a JSP/JDBC layer to replace the