Index
| DICOM Analysis - My Device Can't Send To PACs Cannot View CHM Over LAN or Internet |
Δ Cannot View CHM Files Over LAN or Internet Δ Solution: Run "regsvr32 hhctrl.ocx" command from the command line to register the library in the system. Δ Solution: Remove the '#' (hash) character from the directory name. Also avoid using '?', '&', and '+' characters in directory names. Δ Solution: Run Windows Explorer, right-click on the CHM file, and select Properties from the popup menu. Click on the Unblock button immediately below the Advanced button on the General page. Click Apply to show the content. Once the CHM file has been unblocked, the Unblock button disappears. Δ Solution: Modify the ItssRestrictions registry entry to enable a specific security zone. For most CHM files, the value of 1 should be enough to allow use without opening up access from/to remote CHM files in email/internet locations. Warning! Enable only those security zones that you trust. Do not enable security zones about which you are not sure. 8.
Use MJ's Help Diagnostics to ensure that all the help viewer components are properly installed and registered.
http://helpware.net/downloads/index.htm
9. Delete the file hh.dat, which you should find in this subdirectory:
\Documents and Settings\%username%\Application Data\Microsoft\HTML Help This file stores information about all the HTML Help files on your system (Favorites, window size and position, etc.), and can cause the files to misbehave if it has somehow been corrupted.
Δ DICOM Analysis - My Device Can't Send To PACS!
DICOM communications occur at the applications level using TCP/IP to communicate between systems.
This standard is what allows the various imaging devices, servers, workstations, film printers and network hardware to perform DICOM transactions between devices regardless of vendor or platform. When you get the inevitable call, I can't send my images to PACS!,
you are set into action. If you are new to the IT side of PACS however, you may
ask yourself, Where do I start? Your goal to resolve these types of issues will be to employ a plan that allows you to immediately eliminate the factors that are currently causing the issues. Now I know that may sound elementary but it is the most critical step to quickly identifying the issue and resolving it. You can create a list of questions that can drive your troubleshooting actions and eliminate items. Remember to think calmly and logically. Step 1. Try to ping that device. If you can ping the device, go to step 2. If you cannot ping the device, try to ping other known devices on that subnet. If other devices on the same subnet respond to ping requests, you can focus on that specific device. IF other devices do not respond to a ping, you may need to start looking at the local switches.
Example ping device: go to start > run > cmd > type ping 199.199.1.1 Step 2. Try to ping the PACS servers. If you can ping the PACS servers, go to step 3. If you can't ping the PACs servers you have major problems, restart PACS serves or the servers themselves. Example ping server: go to start > run > cmd > type ping 199.199.1.99 Step 3. Access the DICOM logs on the PACS server and look for the DICOM send from the device that is having the issues. Typically, the DICOM logs are stored by AE title or you can search the log files for the AE title that is having issues. The log files will tell you if there is some DICOM specific issue. I.e. Disk space is full; the AE title is unknown (sometimes a device upgrade will reset all the DICOM configuration) or some aspect of the DICOM association is failing and why. Example access: access logs either by UNC
\\servername\logs or log into server and navigate to logs folder REMINDER! This is not the definitive or the absolute way to troubleshoot when a device cannot send to PACS but merely a way to get started.
Δ How To Wire RJ45
568A & 568B Wiring
Straight Through Cable RJ45 RJ45 Pin # Connects To Pin # 1 <--------> 1 2 <--------> 2 3 <--------> 3 4 <--------> 4 5 <--------> 5 6 <--------> 6 7 <--------> 7 8 <--------> 8 Crossover Cable RJ45 RJ45 Pin # Connects To Pin # 1 <--------> 3 2 <--------> 6 3 <--------> 1 4 <--------> 7 5 <--------> 8 6 <--------> 2 7 <--------> 4 8 <--------> 5 Rollover Cable RJ45 RJ45 Pin # Connects To Pin # 1 <--------> 8 2 <--------> 7 3 <--------> 6 4 <--------> 5 5 <--------> 4 6 <--------> 3 7 <--------> 2 8 <--------> 1 Crimpers Wire RJ45 End
You're surfing along the internet and happened to come across a chm microsoft help file. You go to view it and it seems like your CHMs are all corrupted. They show a "The page cannot be displayed" or "Action canceled" error in the right-hand pane of the CHM viewer. There are several possible reasons why your CHM e-books and documentation files are unreadable.
What Microsoft says about this: Link
So, here is what the error looks like:
Here are the solutions and screenshots I have compiled:
The CHM viewer component is not properly registered on your PC
The system file \system32\hhctrl.ocx may get missing, corrupted, or unregistered. 
Your CHM files are stored in the folder with '#' (hash) character in the path
Many C# developers discovered that their documentation and e-books in CHM format cannot be read because they were storing their CHM files in the directories like 'C:\E-books\C#\'
The hash character signifies an anchor in HTML so the CHM viewer fails to resolve the path properly and to retrieve the content. 
A security update for Windows XP may block access to CHM files
Windows XP security update blocks active content in CHM files to protect your system security. Additional information is available here. 
The CHM file is in the restricted Internet zone
When a CHM file that you are trying to access is stored remotely, e.g. on the network drive or on a remote server, you may also get in trouble. If the associated security zone is restricted, then CHM files won't be displayed as well.
Follow these steps:
1. Run 'regedit' command from the command line.
2.
Locate and then click the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions
Note: If this registry subkey does not exist, then create it.
3. Right-click the ItssRestrictions subkey, point to New, and then click DWORD Value.
4. Type MaxAllowedZone, and then press ENTER.
5. Right-click the MaxAllowedZone value, and then click Modify.
6. In the Value data box, type a number from 0 and 4, and then click OK.
The values settings are
0 = My Computer
1 = Local Intranet Zone
2 = Trusted sites Zone
3 = Internet Zone
4 = Restricted Sites Zone
7. Quit Registry Editor.
10. Delete Internet cache.
I had a job interview where knowing a little bit about DICOM would be a plus. So I delved into the technology and found out that I knew more than I thought. Working in the healthcare industry for the past 8 years has shaped me into a pretty well-rounded administrator. I count myself very lucky to have had the opportunity to be exposed to so much technology on a daily
basis.
So what is DICOM? Let's start off by defining what DICOM is. DICOM is digital imaging and communications in medicine. It is a standard that defines how medical imaging information is handled, stored, printed and transmitted. It also defines a network communications protocol and the file format.
Troubleshooting PACs calls tend to be networking issues or server issues rather than issues related to DICOM problems. However, this page will help develop the list of questions you need to ask in order to communicate between systems.
| Having some basic troubleshooting skills can go a long way in determining
where
| the problems are, what the solutions may be, and how to implement
those
| solutions.
|
| One of the most important troubleshooting skills you can
develop is OSI
| Model knowledge. It's a 7 layer abstract model that
basically breaks
| up communication and design of the entire digital process; it's a kind of workflow.
| What this means to you, if utilized properly,
it can actually show where the
| problem lies and the most likely
solutions. I will not go into detail on the layers
| because you can
find that anywhere on the internet, but what I willl give you is
| an example
of just how useful it is.
|
| The 7 layers are physical-data link-network-transport-session-presentation and
| application. So let's say you get a call that the PACS is down. And your question
| will of course be, what exactly do you mean down? Well, they say, I can get to PACS
| but no one in radiology can. Right away, you bring up the OSI Model in your
| head. You verify that
customer can actually get to PACS from her workstation,
| and she can. That tells you that ALL 7 of the layers are working for this user. So
| right away, you want to try to ping a workstation in radiology...you do not get a
| response. Because you now know for fact that the PACS system is up, but certain
| workstations cannot communicate with it, this will lead us to believe that
| this sounds like something between the network and physical layer issue in
| that department. Well, you ask, what happens at
the network-physical layer?
| Switching, routing, addressing and bits on a wire.
|
| This tells you that the problem lies somewhere between network and
| physical. Let's rule out cut wires-physical, addressing problems-datalink, routing-
| network, because on this segment there are no routers, that leaves us with
| switching. So you walk over to the wiring closet, and peak inside, and low and
| behold, the radiology switch appears to be locked-noticing it has all lit amber
| lights! You power cycle the switch, walk over to the rad department, and sure
| enough, they are communicating once again with
the PACS.
|
| Now with a little experience with the OSI Model, not just the layer 2
| issues, but many common PACS problems and other IT related issues will receive
| faster attention in the precise areas where you should be examining. There is
| nothing more frustrating than not
knowing where to begin troubleshooting.
| Learn how to use the OSI Model and you will thank yourself later.
|
| Here are a few OSI Model links:
|
|
Link 01-info
Link 02-troubleshooting
Link 03-video01
Link 04-video02
* article compiled from link
What is a RJ45? The
RJ45 plug is an 8-position modular connector that looks like a large phone plug. It is attached to a wire which then commonly allows your computer to be
connected to a network; allows your computer to communicate with other
computers.
T568A and T568B are the two color codes used for wiring eight-position RJ45 modular plugs. Both are allowed under the ANSI/TIA/EIA wiring standards. The only difference between the two color codes is that the orange and green pairs are interchanged. T568A wiring pattern is recognized as the preferred wiring pattern for this standard because it provides backward compatibility to both one pair and two pair USOC wiring schemes. The T568B standard matches the older ATA&T 258A color code; the most widely used wiring scheme. It is also permitted by the ANSI/TIA/EIA standard, but it provides only a single pair backward compatibility to the USOC wiring scheme. The U.S. Government requires the use of the preferred T568A standard for wiring done under federal contracts.
Now what does all this mean to you? The skill you need to acquire will be how to wire a jack. So 568A and 568B will be the wiring schemes. Let's take a look at our diagrams:
Wiring Table With Pin Outs
What You Will Need To Wire Jack
About
I'm a Computer
Systems Engineer
Living and loving life
........................................
Author
