In support whether we do data transfer or not?
hi experts,
i heard from my friend, that all the data transfers will be completed before the go live and no data transfer will take place after that or in support.
so i have doubt regarding this. whether in support project will there be any of data transfer or not. if yes what kind of things are transferred?
regards,
sri.
generally it is transactional data which is transferred regularly even after go live..but for that set ups and coding done only during go live ..
in support there are only few changes u have to do as per bugs found during real time..:)
hope this ll help ur doubts...reward points..
cheers
Similar Messages
-
Does iPhone SDK support the feature of data transfer via Bluetooth or USB?
Hi,
I'm developing a application in which I want a feature for data transfer either using Bluetooth or USB.
Does iPhone SDK support this feature of data transfer via Bluetooth or USB?
Please help me.
Thanks.The SDk doesn't deal with BlueTooth or USB. Your only option is wireless data. (WiFi, 3G, etc)
-
N95 8Gb USB Data Transfer Mode not working
I have a bizarre problem with USB Data transfer.
a) I upgraded to the new 15.x firmware with the correct HKCSL package - 0557980
b) I connected PC #1 in data transfer mode with no issue and copied a bunch of installers onto the mass memory and went on to install them - to the PHONE memory.
c) Later in the day, connected PC #2 and did the same with the last few applications.
d) Next day tried to connect PC #1 and it didn't work
e) Thought I must have an application using the MASS storage but checked and not so - all apps on Phone memory.
f) Went to PC #2 and tried - Data transfer mode works - no problem.
g) Tried PC #1 again, and still not working. I get all the right messages (Mass storage cannot be used at this time etc) on the handset, and I get the "safely remove hardware" option appearing on the PC - but I don't get a drive letter assigned in the Windows Explorer.
h) I have tried it on PC #3 and this works as well - no problem.
1. The working PC's both have PC Suite 2-Beta installed, while the problem PC has no PC suite at all.
2. I have downloaded the Nokia-connectivity_cable_driver_rel_6_85_10_0 and it installs properly - giving all the expected wireless... options in Device Manager, but I still don't get a drive letter assigned with the basic data transfer mode on this problem PC #1
So the issue seems to be with a PC that has never seen any version of PC suite, but it worked straight after the firmware upgrade.
All PC's are XP SP2.
Any suggestions on anything else to try ?
RegardsSOLVED by:
- attaching N95, selecting USB Data Transfer Mode
- Going to Device Manager
- Selecting the USB Mass Storage Device for N95
- "Uninstall"
- Remove cable when N95 says its safe to
- Re-attach cable
The PC then re-discovered and reloaded the drivers including the mass storage which then worked normally.
No idea what messed it up in the first place though. -
Init without data transfer is not working in the Production box for FICA extractors
Hi Guys,
We are unable to do Init without data transfer for FICA Extractors(0FC_INVDOC_XX) from BODS system. And the job is successfully completed from the BODS end but it is not hitting the source system.. Can any one please let me know how to resolve this issue.
Thanks,
KovurHi,
After triggering your info pack with init without data transfer, are you able to see delta pointer at info pack-->scheduler--> init options source system.
Are getting any error message? if yes then please share here.
Thanks -
Upgradation issue 4.6C to 4.7 for DP90-Data transfer module not allowed
Hi All.
We have a issue in upgradation project form 4.6C to 4.7.
Process we follow is Contract,Notification,Service order,Debit memo request.
While doing DP90 for service order we are facing a error as <b>Data transfer module is not allowed</b>
Afetr this system gives you only option to EXIT.
In the log display we get following message :
Data transfer module is not allowed
Message no. V1247
Diagnosis
A wrong data transfer module was entered in Customizing for copying control. When you enter a sales order with reference to a quotation, you cannot copy header data from an invoice, for example. The module number is 306.
System Response
Processing is terminated.
Procedure
Check the copying control for your transaction in Customizing or contact your system administrator.
Any idea how to deal with this
Regards,
Amrish PurohitHi Amrish,
There is a standard SAP program: SDTXT1AID. Start it, and the upper section you can find your incomplete parameters. Sign your relevant parameters (or all) and F8
(not test case).
I hope it will help you.
regards,
Zsuzsa -
NI8451 SPI data transfer speed and SCLK setup time adjustment
I'm using NI USB-8451 SPI bus to do communication. I can not reach the speed of communication 4MHz (NI USB-8451 module advertises speeds up to 12MHz). Actrually the data transfer speed is much slower than 4/8 Mb/s. The 16k*16bit data cost around 800ms while it should be 128ms if the data transfer achieves 4Mhz speed. In the manual there is a SPI timing clock figure like this:
In the 4Mhz communication case, the t2 should be 0.25us. I wonder whether the low data transfer speed is due to t1,t3 and t4 since they occupy too much "dead time". If my guess is right, is there any method to reduce the t1,t3 or t4, espetially t3? I know that in the advanced API there is a way to add delay while I did not figure out how to reduce delay(t3). If my guess is wrong, what is the exactly maximum data transfer speed NI8451 can support? (not the clock rate)
Thanks for help.Hi everyone. Im using the SPI communication with 8451 and Im having the same situation., since the serial flash memory I need to program is big enough, t3 (SCLK Setup time) and other "dead time" which I think is the time when buffer on the 8451 needs to be re-filled those are killing my expectation on the final results. I can't see a way to decrease t3 (~10uSec) and in the same way Im seeing something like buffering up to 100~110 bytes then, a ~1.5mSec delay appears on the signal waveforms. Did somebody have good results trying to avoid this?
Thank you.
Javier
Attachments:
t3 - SCLK setup time.jpg 156 KB
Data byte Transfer_109.jpg 137 KB -
ALE Data Transfer Issue--Needs Immediate Attention
Hello Gurus
I am hoping somebody can guide me here--
We are on E-Rec 603 with seperated standlone e-rec system.
we have set up ALE Data transfer for object type P from ECC QA to E-Rec QA system but unfortunately the I-Doc is always gettign posted with status 52 ( application document not fully posted).
The infotypes 0000,0001,0002,0006 and 0105 are being transferred. The report HRALXYSNC refuses to recognise the 'P' object transferred and says=='data not found for search condition'.
We debugged HRALXSYNC and found that IT 0003 needs to be included but we tried transferring that too--however, the ALE still fails to transfer the data.
Not sure why the data transfer is not happening--what is the best alternative?
Would really reallly appreciate some light....!!
Thanks
TaniaHello Tania,
first of all we should have a look on your system landscape. If you have e-recruiting on an standalone server, the server installation should only include basis components (BASIS, ABA, PI, ...) and the e-recruiting component. Running e-recruiting standalone on a server with a complete ERP installation is not officially supported up to EhP3.
Could you please check that you either have the first landscape situation or if you have installed a full ERP implemented note 1147882.
Before running some ALE at all ensure that the system works well and w/o any SLG1 entries for external candidates and internal candidates created using report RCF_CREATE_USER.
Then make sure the BAdI implemtations are set accorting to note 997181:
BAdI Implementation
HRALE00SPLIT_INBOUND HR_INB_PROCESS_IDOC -> activated
HRALE00INBOUND_IDOC HRRCF00_DELETE_SPREL -> activated
HRSYNC_P CONV_HR_DATA_TO_EREC -> deactivated (if existing)
HRALE00INBOUND_IDOC HRRCF00_INBD_NEWMOD -> deactivated (if existing)
For the distribution model define a filter restriction the infotypes / subtypes destributed for P to:
Infotype 0000
Infotype 0001
Infotype 0002
Infotype 0006 Subtype 0001
Infotype 0105 Subtyoes 0001, 0010
If you want to include the OM in E-rec (use positions in requisition maintenance, etc.) add a filter for Infotypes 1000 and 1001 for objects P, S, O and C (you can use the subtype to restrict relations and avoid unnecessary relations in the IDoc. P->CP relation is only necessary for EhP 4 and higher.
Make sure you use the best practise step by step descripion for the intial data transfere for EhP 3 documented in note 997181 document Two_Instance_E-REC_Integr_ERP_EN.pdf page 4, add the processing for type C after each object type S step.
Hope that helps.
Kind regards
Roman -
How to enable delta without data transfer option for Collections - Extracts
Hi All,
My question is basically related to FSCM - Collections related data sources and Init and Delta loads of the same.
Once the Init is completed, I wanted to do delta without data transfer and option is graded out - means can not really select the option for Collections Data Sources ..
For Example I have OCLM_INVOICE as my data source which has lot of data to extract - and in the Init stage itself, its either giving errors or keeps running for longer time (Records to be extracted is ONLY 400000) and finally shows in the monitor as 400000 of 0 Records..
And also Is there any place where I can find that all of Collection data sources are TIME STAMP based or other options.
I appreciate your quick an ddetails reply and points will be awarded for sure.
Thanks
AK.As far as I remember there some datasources which wont support init w/o data transfer. I guess COPA is one of them. I havent worked on datasource 0CLM_INVOICE but it is possible that even this could be same case. When I seached on help.sap.com for this datasource, I found this info -
(I am pasting content because strangely the webpage doesnt give html link for this search result window)
DataSource Transactional Data: 0CLM_INVOICE
This DataSource is used to extract the transaction data of an invoice from Accounts Receivable Accounting (FI-AR). The system determines the key figures from the amounts of the line items belonging to the invoice. The date fields each contain the respective date of an action that refers to a line item. The extractor provides the data in optimized form for SAP Collections Management.
Technical Data
Application Components Collections Management (0FSCM-CLM)
Available as of Release mySAP ERP Value Pack 2005.1
Shipment SAP NetWeaver 2004s BI Content Add-On 3 SP02
Content Versions There are no content versions.
RemoteCube-Capable No
Delta-Capable Yes
Extraction from Archives No
Verifiable Yes
Data Modeling
Delta Update
The DataSource permits delta update with generic delta processing using the time stamp. The system determines the invoice reference for a document in Business Transaction Event (BTE) 5010 and saves it with a time stamp. In the case of a delta upload, it determines the amounts of the line items based on these document numbers.
Extractor Logic
Verification of Key Figures
If necessary, you can check the key figures of the individual customers as follows:
In the source system, from the SAP Easy Access screen, choose the following function: Accounting u2192 Financial Supply Chain Management u2192 Collections Management u2192 Integration with Accounts Receivable Accounting u2192 Process Receivables (Old).
Enter the required customer.
The Customer Account - Process Receivables screen appears. Here you see a list of all invoices for which there are open receivables.
Using this list, you can compare the following key figures:
Original Amount of Invoice or Credit Memo (INVOICE_AMOUNT)
Amount Paid (PAID_AMOUNT)
Open Amount (OPEN_AMOUNT)
Total of All Credit Memos for Selected Invoice (CREDITED_AMOUNT)
Amount Arranged for Payment (PAYMENT_ARRANGED)
Unsychronized Backup Recovery in BW System
If you import backup copies asynchronously, you have to initialize the delta procedure for the DataSource again.
Abhijit
Edited by: ABHIJIT TEMBHEKAR on Nov 18, 2008 5:00 PM -
If bi-directi​onal parallel data transfer possible in DAQ 6009???
want to interface AVR to DAQ6009 via parallel 8-bit bus but I need it to be bi-directional thus stuck at this point since m nt sure whether bi-directional data transfer possible or not
Solved!
Go to Solution.First of all, serial port is available on win7. Silly to say that it's not. Since it is a single bit, mention of it is irrelevant, as is USB.
Second, the lines of the 6009 can be either input or output. A line cannot be both so you would need to stop your task, change the line direction, and start a new task.
Third, you say there is no protocol for the AVR yet you ask for an example. If you don't know the protocol, you need to read the data sheet and understand it. I'm going to assume that you mean this AVR.
For digital I/O examples, see Help>Find Examples. As mentioned, the 6009 is strictly software timed so you will be limited to 'bit-banging' per the device's specs and if it has a minimum clock rate, find other hardware. -
How to find the max data transfer rate(disk speed) supported by mobo?
I plan on replacing my current HDD with a new and bigger HDD.
For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
Here's dmidecode:
# dmidecode 2.11
SMBIOS 2.5 present.
80 structures occupying 2858 bytes.
Table at 0x000F0450.
Handle 0xDA00, DMI type 218, 101 bytes
OEM-specific Type
Header and Data:
DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
FF 00 00 00 00
Handle 0xDA01, DMI type 218, 35 bytes
OEM-specific Type
Header and Data:
DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 04/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: OptiPlex 755
Version: Not Specified
UUID: 44454C4C-5900-1050-8033-C4C04F434731
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0200, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0PU052
Version:
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Space-saving
Lock: Not Present
Version: Not Specified
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: 76 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 6
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Not Specified
Voltage: 0.0 V
External Clock: 1333 MHz
Max Speed: 5200 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
Handle 0x0800, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2
Handle 0x0801, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0802, DMI type 126, 9 bytes
Inactive
Handle 0x0803, DMI type 126, 9 bytes
Inactive
Handle 0x0804, DMI type 126, 9 bytes
Inactive
Handle 0x0805, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB2
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB3
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0808, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB4
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0809, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB5
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB6
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB7
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB8
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ENET
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x080E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MIC
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0810, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-IN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0811, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HP-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0812, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x090A, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT1
Type: x1 Proprietary
Current Usage: In Use
Length: Long
Characteristics:
PME signal is supported
Handle 0x0901, DMI type 126, 13 bytes
Inactive
Handle 0x0902, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0903, DMI type 126, 13 bytes
Inactive
Handle 0x0904, DMI type 126, 13 bytes
Inactive
Handle 0x0905, DMI type 126, 13 bytes
Inactive
Handle 0x0906, DMI type 126, 13 bytes
Inactive
Handle 0x0907, DMI type 126, 13 bytes
Inactive
Handle 0x0908, DMI type 126, 13 bytes
Inactive
Handle 0x0A00, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: Intel Graphics Media Accelerator 950
Handle 0x0A02, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: Intel Gigabit Ethernet Controller
Handle 0x0A03, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Controller
Handle 0x0B00, DMI type 11, 5 bytes
OEM Strings
String 1: www.dell.com
Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0F00, DMI type 15, 29 bytes
System Event Log
Area Length: 2049 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFF01000
Status: Valid, Not Full
Change Token: 0x00000018
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: System limit exceeded
Data Format 2: System management
Descriptor 3: Log area reset/cleared
Data Format 3: None
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x1100, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_1
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: AD00000000000000
Handle 0x1101, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_3
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1102, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_2
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1103, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_4
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FDFFFFFF
Range Size: 4064 MB
Physical Array Handle: 0x1000
Partition Width: 1
Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1402, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1102
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1403, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1103
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1410, DMI type 126, 19 bytes
Inactive
Handle 0x1800, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Enabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Enabled
Front Panel Reset Status: Not Implemented
Handle 0x1900, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: *-* 00:00:00
Handle 0x1B10, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00
Handle 0x1B11, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD01
Handle 0x1B12, DMI type 126, 12 bytes
Inactive
Handle 0x1B13, DMI type 126, 12 bytes
Inactive
Handle 0x1B14, DMI type 126, 12 bytes
Inactive
Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x8100, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 00 81 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x8200, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
00 00 00 00
Handle 0x8300, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
Handle 0x8800, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 00 88 5A 5A
Handle 0xD000, DMI type 208, 10 bytes
OEM-specific Type
Header and Data:
D0 0A 00 D0 01 03 FE 00 11 02
Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 78 03 07 03 04 0F 80 05
Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 F8 03 04 03 06 80 04 05
Handle 0xD201, DMI type 126, 12 bytes
Inactive
Handle 0xD400, DMI type 212, 242 bytes
OEM-specific Type
Header and Data:
D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
00 00
Handle 0xD401, DMI type 212, 172 bytes
OEM-specific Type
Header and Data:
D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
BF 00 69 01 56 BF 40 FF FF 00 00 00
Handle 0xD402, DMI type 212, 152 bytes
OEM-specific Type
Header and Data:
D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
65 FC 01 FF FF 00 00 00
Handle 0xD403, DMI type 212, 157 bytes
OEM-specific Type
Header and Data:
D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
52 BF 40 45 02 52 BF 00 FF FF 00 00 00
Handle 0xD800, DMI type 126, 9 bytes
Inactive
Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
00 00 00
Handle 0xDD01, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
00 00 00
Handle 0xDD02, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
00 00 00
Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
Handle 0x7F00, DMI type 127, 4 bytes
End Of Table
Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf says that it is 3.0Gb/s
and here's hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD800JD-75JNC0
Firmware Revision: 06.01C06
Standards:
Supported: 6 5 4
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156250000
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 76293 MBytes
device size with M = 1000*1000: 80000 MBytes (80 GB)
cache/buffer size = 8192 KBytes
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* Gen1 signaling speed (1.5Gb/s)
* Host-initiated interface power management
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct
Last edited by Inxsible (2011-03-27 04:40:49)I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
Anyhoo, while I was in the BIOS I found two things which I had questions about :
1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
I will edit this post and let you know exactly what settings were present under the Virtualization sub-section. -
If DVD Movies, Audio CD's and even burning CD and DVD's are not supported, what is the point of DVD & CD Sharing then? Wouldn't it just be better to remote in or use a thumb drive if it's only able to be used for data transfer?
Or am I missing the bigger picture?As long as you have a Superdrive or an external burner/drive, burning, watching, installing, etc. from CD or DVD will work just fine. And so will sharing.
-
Revision: 11205
Author: [email protected]
Date: 2009-10-27 15:04:26 -0700 (Tue, 27 Oct 2009)
Log Message:
Fix bug FM-169: Trait support for data transfer sample doesn't display bytes loaded and bytes total for SWF element
Ticket Links:
http://bugs.adobe.com/jira/browse/FM-169
Modified Paths:
osmf/trunk/apps/samples/framework/PluginSample/src/PluginSample.mxml
osmf/trunk/apps/samples/framework/PluginSample/src/org/osmf/model/Model.asThe bug is known, and a patch has been submitted: https://bugs.freedesktop.org/show_bug.cgi?id=80151. There's been no update since friday, so I wonder what the current status is, or if it's up for review at all.
Does anyone know how we can be notified when this patch hits the kernel? -
Is there any support for data transfer compression in oracle XE?
Hi
Thank you for reading my post.
I am wondering whether it is possible to ask database and JDBC driver to use some sort of compression for data transfer?
I want to reduce the network workload as much as possible.
ThanksAFAIK, Not directly from Oracle.
-
Is data transfer included in the 90-day tech support which comes with a new MacBook Air?
I would think so. A friend is buying a new MacBook Air, and needs to know if data transfer is included in the 90-day technical support offer from Apple. I'm pretty sure it is, but just would like to make sure I'm steering her in the right direction.
Thanks.Instructions yes, performing the actual data transfer, not likely. Here are a couple of links that may be useful:
http://pondini.org/OSX/Setup.html
http://support.apple.com/kb/HT5872
Ciao. -
Unsuccessful data transfer onto my new macbook pro- please help
I have just upgraded to a new 2.16GHz core 2 duo macbook pro and tried last night to transfer my data via firewire using the apple start up set up from my previous 1.83GHz core duo macbook pro bought in March 2006. Unfortunately there were errors in transferring my user folder. I subsequently used migration assistant with the old macbook pro in target disc mode and the same error occurred. I have now manually transferred my user folders by dragging them from the target disc old macbook pro drive into my new user folders in the HD of the new macbook pro. Please can anyone advise me whether this is all I need to do to have my user files on the new macbook pro ie are there any other files I should move over from the old to new computer? The applications transferred in the initial set up and several folders in my HD and it seems only the user folders didn't.
Can someone explain why this happened also please? I have checked the new HD with disc utility and it has no errors.
I have transferred files from several powerbooks in the past using the initial set up or migration assistant and haven't had problems like this before? I wonder whether the new computer is faulty? Please can anyone advise? ThanksWelcome to the Apple Support Communities
You can only sync the iPhone with one Mac or PC, so your Mac is asking you to erase the device because you synced it with another Mac or PC. To avoid this, I recommend you to copy the "iTunes" folder of your old Mac or PC (in Music folder) to the Music folder of your Mac, so you'll have the same data on your Mac as the data you had on the PC.
To transfer contacts, notes, etc., I recommend iCloud > http://www.apple.com/icloud/setup/
Maybe you are looking for
-
Reporting Services username and password prompting
We have several branch office locations and one reporting services server. All of the branch office locations can access the reporting services server, but we have one location for the passed week, each time they make a connection to this server, it
-
Limit on the number of photographs in Photo Layout Creation v5.0?
Hi, Moving from PSE v4.0 to v5.0 Adobe changed the way Photo Album pages and Photo Layouts are created. In v5.0 and greater the photos are now loaded into Elements Editor and that is where the creation is then made. The problem is that I find the Edi
-
Apple TV / TV optimal settings?
Hi I love my gadgets but I'm a little bit thick when it comes to some parts of operation / set-up. I've got an Apple TV and Toshiba Regza AV Series HD Ready TV. I've set it up to what I think is the optimal setting for screen etc but I'm now doubting
-
Hi Experts, We have recently implemented E Payment through F110 PWM. We have created one Z format through DMEE and assign same to all required payment methods. While executing the F110 & selecting the create payment media check ,system authomatically
-
Compiling "write to jpg\bmp\png file" in Labview2011
Hello everyone, I'm trying to compile a source code written in Labview 8.5 into Labview 2011. In the old source code I used the "write BMP/JPG/PNG file" VIs. I noticed that these VIs have changed in Labview 2011. Either way (using the old or new VIs)