Sol Man 4 - data transfer to SMD - what is installation path?
In Solution manager 4, transactio SOLUTON_MANAGER then select menu path goto > Solution Manager Diagnostics > Solution Data Transfered. It says "This wizard senden the configuration data of solutions to the Solution Manager Diagnostics.". Select continue. Next I select a Solution Landscape and press continue. It seems to select all the servers with a basis level >= 640 and in my case find red opposit the server. If you double click on the server and expand the resulting display to the "SYSTEM - main instance" attribute Installation Path is blank.
What is Installation Path? Nothing I try to enter is valid. Any idea what is supposed to go here?
Before you attempt to publish a landscape to SMD there must be an SMD agent on each host running SAP BASIS 640 or higher that has sucessfully connected to the SMD. The wizard takes your specified path and asks the agent on that host to verify that it exists. If there is no agent you get that same cryptic error message.
I suggest you use SM trans SOLUTION_MANAGER to create landscapes comprising of systems you have sucessfully deployed a SMD agent there-on. As you deploy more SMD agents you can either create more landscapes or add those systems to your existing landscape that you have used for "publish to SMD".
Summary:
Step 1) Install SMD
Step 2) Install SMD agent(s)
Step 3) verify http://smhost:smport/smd/admin > Agent administration > Agent tab lists your server(s)
Step 4) create landscapes for publishing wizard
Step 5) publish lanscape expressly tailored for SMD
Similar Messages
-
Data transfer rate Airport Extreme
which is the data transfer rate of the USB port in the Airport Extreme (4ta. Generation)...???
The HDD installed in that port, reads and writes very slowI executed the test and I have a rate of data transfer of 1.9 escrtura of Mb/s and 2.7 reading Mb/s…. this is very under… What I can do.?
I even reinitiated the Airport and itself with the problem. I directly tested with the ports of iMac, and have DRT of 25.8 and 18.4 Mb/s
Ok, I am assuming that your measurements are in Mega Bytes per Second (MB/s) and not Mega Bits per Second (Mb/s). Even so, I would agree that you are getting low data transfer rates.
What is the make and model of the USB HDD that you have attached to the AirPort Extreme? Is it formatted in HFS+ or FAT32?
Also, the 25.8 & 18.4 readings when you have this drive attached directly is a bit low as well. I would expect something more like: 35 MB/s (read) & 25 MB/s (write) for a USB 2.0-connected HDD. -
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.
-
What is the "Data Transfer Process" in the BI7.0, and how does it work?
Hi, experts !
I'm fresh on BI7.0.
What is the "Data Transfer Process" in the BI7.0, and how does it work?
And what is it used for ?
Could anyone help me? Plz send me some doc.
[email protected]
Thank u !HI,
Refer this blog
/people/community.user/blog/2007/06/22/sap-netweaver-70-bi-data-transfer-process-dtp-blog-series
Also refer
http://help.sap.com/saphelp_nw2004s/helpdata/en/42/f98e07cc483255e10000000a1553f7/frameset.htm
Thanks -
Whats the maximum achievable speed of data transfer from RT to host PC
Hi
Anybody can tell me whats the maximum achievable speed of data transfer from RT to host PC, in case of both PXI and CompacRIO.
Regards
VisumanHi visuman,
To be honest, the dataspeed is dependent on how you architect the code, and the data communication channels that you use.
There are many factors that influence the maximum transfer rate, including network topology, types of interface used, OS, ambient network traffic etc.
You can control two things, packet size, and amount of sleep time between transmissions.
By altering the delay between consecutive TCP/IP transmissions and by varying the packet sizes sent from the embedded side to the host side, you can obtain a clear picture of network characteristics between the two devices. The end result is a report of the optimal TCP/IP configuration, that is packet size and sleep time.
Check out : Developer Zone : Measuring the Maximum Amount of Data Sent Out of a Real-Time Target Device
Here are some other links that maybe useful for you.
KB 2M9ARPEW : Real-Time VI to Host VI Communication Methods
Developer Zone : Real-Time FIFO for Deterministic Data Transfer Between VIs
Hope this helps!
Ashish Naik
Field Sales Engineer
National Instruments UK -
i was just copying my data from stand by phone by using phone to phone data transfer but phone also locked with i cloud login of stand by phone what to do
If it's a hardware problem, then the phone will need to be replaced.
There is no magic that can fix a hardware problem. -
What is the difference between copy requirement and data transfer routines
Hi Experts,
I am writing a copy control routine for maintainence quote
from sales quote.Where do i have to write it in VOFM?
Is it in copying requirements or data transfer.
Actually according to the business all the line items from the sales quote are copied
into the maintainence quote and additional line items are added into maintainence quote
and the line items copied from the source document are linked to the two newly added
line items.
Please advise.
And is it possible to add the 2 new line items to the new document into VBAP at the runtime?
Regards,
ChitrasenFirst of all you have to have a link between the sales documents. You can check it in Tcode: VTAA. if not, talk to your functional people. Try to make this equal to quote to order but instead make it quote to quote.
You need to put break point in copy requirement as well as in data transfers and check for your requirement.
Well, the code you want to put in will be the requirement
I am not sure if you can add 2 line items runtime into quote. this has to go through different checks and i dont think it is possible.
Good luck -
Some more information on the above: OS: 7.2
1. None of the shutdown commands would work so I held the power button down and received a prompt that asked if I wished to force eject the drive, I selected
the force eject and then shut down.
2. Just recently I installed an eSATA _ Thunderbolt_ port multiplier compliant PCIe card (Seritek Q6G) into a thunderbolt external chassis (OWC Helios) (seritek Q6G).
This freeze data transfer also happened when I connected a Firmtek 5PM external tower to the iMac via thunderbolt cable.
The driver for the seritek Q6G was installed in the iMac previous to connection of any of the devices.
Both external towers mount ok on the iMac but have frozen during data transfer.
The initial freeze was with the Firmtek 5PM which is (JBOD)_ I thought that might have had something to do with the freeze_ it being JBOD_ so next I tried the Mercury Elite AL Pro Q2- which is formated in RAID 5. But then froze too.
Anybody have any experience with this?
Maybe I need another driver?
Or maybe some update to my OS?
Any suggestions welcomed.
Thank youHello BDAqua, thanx for the suggestions. Before I saw this reply I tried to first quit the finder and then to relaunch the Finder but that resulted was a blank gray screen.
In the end I ended up having to power down the iMac.
Fortunately the RAID array that was "active" seems to be fine and also has a firewire 800 connection so I can use it_ just not with thunderbolt until this issue is solved.
I'm going to check in the Applications>Utilities>system log to see if any clues are evident_ thank you for the suggestion.
PS: Nothing of note was obvious as a root cause in the Activity Monitor though.
hmmm....I was told that the Helios and seritek card were compatable and that the Helios didn't require any drivers..it will be a drag if there isn't an easy fix for this since this new PCIe card from seritek is the first to offer port multiplier compatibility for eSATA to thunderbolt...since they are both new I'm hoping that an OS upgrade will be the fix (presently7.2)...we shall see. -
What is hierarchical data transfer in functional location
hai,
i want to know indetail about hierarchical data transfer and horizontal data transfer in functional location.
can any one help me in this regard....
plz give information with some example if you dont mind...
thanks in advance
regards
gunnu.Hi
From SAP HELP
Hierarchical Data Transfer
Definition
You can maintain data at a high level within a hierarchical object structure. The system will automatically transfer the data changes to the levels below that are affected.
The maintenance planner group is changed for the clarification plant described in Functional Location. The employee responsible for maintaining the master data makes the change to the master record of the highest functional location C1 and saves the changes. The system automatically makes the same change for all affected functional locations below the functional location C1, and issues a message to inform the employee of these changes.
Horizontal Data Transfer
Definition
With horizontal data transfer you can differentiate between:
Data transfer from reference location to functional location
Data transfer from functional location to installed piece of equipment
The ABC indicator of the functional location C1-B02-1 "Ventilator" is to be changed for several clarification plants.
The employee responsible for maintaining the master data makes the change in the master record of the reference functional location and saves the entries.
The system automatically makes the same change for all affected functional locations that were assigned to this reference location and for the pieces of equipment that are installed at these locations. The system then issues a message informing the employee of the changes.
Regards
thyagarajan -
Problem in moving project from Old Sol Man 3.1 to New Sol Man 4.0
Hi All,
I am trying to move a project from solution manager 3.1 version to a new solution manager 4.0 version. I followed the below steps:
1.Slected and transported the project using solar_project_admin tcode and created the transort requests in the old sol man version 3.1.
2.Copied the cofile and datafiles from old sol man and kept in trans directory of new Sol man 4.0 version at OS level.
3.Imported the requests into the new Sol Manager 4.0 successfully
4.When I tried to open the imported project it told me to run the "solman_log_comp_mgr program" to convert the project to the central logical components. I just did it and it went well.
I can see the project and do see the document types but no document names and getting all sorts of error messages when I tried to open these documents. Also I dont see the logical components under system landscape.
Before importing, I just have configured servers/hosts, databses and all the components of system landscapes in the new solution manager.
I request you to help me solve this issue. I also would like to know whether i followed proper procedures that i listed above? If not please suggest what procedures I should have follwed.
Thanks in advance.
Aravind SerikarHi Aravind,
to transport a project from 3.1 to 4.0 I would not use SOLAR_PROJECT_ADMIN to "migrate" a project. There for we developed SOLAR_MIGRATION there you can transport system landscape info, also you can transport projects. You should only transport system landscape info if in 4.0 SMSY is EMPTY. To transport projects you have only to specify your project and define a local folder. In this folder we store a few important information. Then all information will be collected in a batch job and automatically exported. Then you have to copy the data file and the cofile into the new trans folder. BUT do NOT forget the i-file. In the folder cofiles you will find a i-file, because we export knowledge warehouse content. This file is important, if you forget it you will get a return code 8. You do NOT have to add the files in the import buffer, we will do this automatically. To import the project, you have to call SOLAR_MIGRATION in SolMan 4.0 there you have to select import, then specify the folder with the few important information. We upload the info and start the import. That is it
Regards,
uDo -
Sol Man 4.0 and Reporting out to BW
We have upgraded to Sol Man 4.0 and need to report the Change Request info, Change Document info and Transports log using an external BW box. In researching this forum, I have learned that we can export data out by activating the CRM business content. I need more guidance as to what DataSources to use. So far we have activated and found data in <b>0CRM_SRV_PROCESS_H</b> and <b>0CRM_SALES_ACT_1</b>, but I am missing information such as Change Advisory Board, Subject, External Reference, Decision Date, and Implementation date to name a few. Can anyone help? Is this documented ANYWHERE?? Thank you.
Charis Davenport
Project Management Specialist
The Walt Disney CompanyDaniella,
Please take a look at this thread.This might help you how to integrate Sol Mngr with Test Director.
Solution Manager integration with Mercury product
Thanks
Sudhan Shan -
Connecting SLD to Sol Man 4.0
Hi all,
I am trying to push my sld data to Sol Man 4.0. I have set up smsy_setup and ran sldcheck and set up sldapicust and everything seems o.k. but when I try to execute the job to pull data (SMSY_SETUP) and I review the update log I see a message stating "the sld server is inactive" and I am not sure why. I can log into sld and it's up an running so I don't know where to turn next.
One thing I do get is when I run sldcheck there is a message saying "No business systems found"?
Thanks,
Rodney MillerHi Rodney,
is the SLD brigde also running?
Go into SLD -> Administration -> Data Supplier Bridge, set update local SLD to true and start the bridge.
Business systems are only needed for XI, but not for what Solman is using.
Regards,
Pascal -
Unable to create EWA in SOL MAN
Hi Experts,
I configured EWA for SOL MAN....
I successfully generating alerts for satellite systems but not for own SOL MAN
Alert running successfully with PMS and Refresh sessins with out error
my RTCCTOOL not showing any errors/requiremwents...
please suggest...
version : SAP SOLMAN EHP1
Regards,
Siva.
Edited by: skreddy555 on Jan 30, 2011 1:38 PMHello,
So you are saying you can generate EWA reports for Satellite systems but not Solman itself?
That really doesn't give any details to the problem, as what has occured and what has not.
Is the EWA scheduled? Have you run solman_setup on Solution Manager as the managed system?
If you want to generate an EWA for Soman itself, then you also need to treat it like a managed system.
IWhat it the status in solman_ewa_adm? Is it active? If it is ther eand active it should be scheduled and then there should
be something in DSWP. Is the icon a bottle? 2 Bottles? A Red Flag? A Grey Diamond, a Document?
Is the maintenace package task scheduled and running with no errors? Are you using the SM_<SID>CLNT<nnn>_BACK RFC or the NONE RFC in SDCN as the back RFC and have you tested them?
Is SM:EXEC SERVICES finishing or cancelling? If it is cancelling is there a dump?
These are some things to check. But it is hard to even gues what the problem is because you have been so vague.
If you can describe what you have done to configure, what is working, and what seems not to be working, this would help to get an idea where & what the problem may be. But you generally need to treat the Solution Manager exactly the same as a satellite system when setting it up for EWA reporting. This make is both a managed and the managing system. So you can't skip any steps just because its the managing system. If you describe the problem in more detail, and if any part in the process is working, and what is not, that is helpful.
You should see it schedulied in DWSP. If not, then it's not scheduled. But the status in DSWP can tell a lot. A Red Flag means a problem with SDCCN tasks or the RFC, a Grey Diamond means important data is misisng and the report can't be generated, so that is a probelm is data collection, two flasks indicates sm:exec services has not run or is failing.
So you really need to give more information....unless I have already touch upon your problem, I don't know how helpful people can be but toss out general information.
I'd like to help more if you can give more details to what you see and don't see that you should.
Regards,
Paul -
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. -
We run a small network in our office consisting mainly of Intel iMacs we purchased several months ago. The server computer is a brand new Intel Mac Pro server with 4 500 gig drives raided together, two 2.66GHz dual core intel processors, all the other bells and whistles we could think of, etc. We added in two fiber-optic switches: one in the server room, one in the office. The switches connect to each other and the server with fiber optic cables, but the iMacs connect with ethernet cables.
We had the iMacs for a while but we just recently got the new server and upgraded our old 100 base switches. Afterwards we wanted to test out the data transfer speeds, as we plan to back up to the server frequently. We were dismayed to find that transfer rates capped out at 60 MegaBytes/sec according to the Activity Monitor's Network Activity tab. In fact, it would range mostly from 40-45MB/sec. None of us here have much experience with networking, but that seemed a tad too slow. My basic math tells me that a byte is 8 bits, and from that a Gigabit network should transfer data at 120 MegaBytes/sec, which is three times the speeds we were actually seeing.
We sent data both to and from the server in order to test this. Thinking it was perhaps a problem with the ethernet itself, we grabbed an external FireWire hard drive and transferred data from one of the iMacs directly to it and noticed exactly the same transfer rates. We plugged two iMacs directly into each other and transferred at the same rate, ~45MB/sec.
Well this was highly frustrating. All Macs supposedly ship with Gigabit ethernet since, what, 2002? Earlier? Why are our speeds so slow? We thought the hard drives might be slow, so we got info on the drives and googled them for their tech specs. The iMacs' Western Digital drives are capable of much much faster speeds according to everything we've read.
We started reading anything we could online that addressed this issue. Some information read the problem might be that the optical DVD-R/CD-R drive was only capable of slower transfer speeds. Since the optical drive and the hard drive are on the same bus it would slow down the hard drive's maximum transfer rate, much like having a Gigabit hub with a 10 base computer plugged into it would slow the entire network down (which is of course why we use switches instead of hubs). Is there any truth to this? If this is, in fact, the case, can we bypass this bottleneck somehow? I'm not talking about opening the computer and manually disabling the optical drive, as that's a waste of a perfectly good DVD-R/CD-R drive.
Also, if this is true, why in blue blazes is Apple flaunting Gigabit ethernet if the computer can only take advantage of 1/3 the speeds Gigabit ethernet has to offer?! I'll happily provide any more information that's relevant to the problem at hand.
Thank you
Mac OS X (10.4.8)Here's the specs for the default Hard Drive that Apple put in here:
http://www.westerndigital.com/en/products/Products.asp?DriveID=137
From that page
Buffer To Host (Serial ATA) 300 MB/s (Max)
Buffer To Disk 748 Mbits/s (Max)
I have no idea what signaling overhead for my data transfer protocol means.
The ethernet cords are no longer than 20 feet, are all Cat5E, and are well shielded. There is little to no ElectroMagnetic interference in any area they run. The longest cable is the Fiber Optic one, which runs about... oh... 40 yards? These were all installed by professionals.
I feel it's important to stress the fact that we tested an isolated direct computer to computer transfer with a single 6 foot Cat5E Ethernet cable and still experienced the same speeds that we experienced over the network. We tested multiple computers, multiple cables, multiple files.
Maybe you are looking for
-
I have been trying to fix itunes for over a week. I had the latest version (32 bit for Vista) and all was well until last week when the shortcut dissapeared. 1. I tried downloading itunes again, but this didn't work. 2. I then tried to do the repair
-
Hi, I am seeking assistant to install my printer with my PC. I misplaced the CD and my computer was acting up that we rebooted and now we can't connect the printer. Let me know if you can help? The serial No. [text removed for privacy]
-
ORA-33156:Positions greater than 2**63 in a dimension map cant be referencd
AWM 11.2.0.1.0A I am trying to view the data from a cube from AWM. (my cube --> cube view --> data). The above error occurs which I have mentioned in the subject column. The cube is a sales cube with dimensions (Date, item, channel, transaction type,
-
Hi, i cannot access my router settings through my browser i know the ip address I'm suppose to go to in my browser but when it asks me for my user i don't know what it is nor my password. I already changed my password on my router do i use that to
-
Play input data in serial connection in speakers ?
Hi. I want to play input data with system speakers. Data receive from Serial Port and I want to play it realtime. my data frequency rabge is between 10 to 500 and it;s amplitude is up to 1. I use this Subvi that I right it for put in final Vi. Sampl