Camera disconnected at Runtime

Hi All,
I am working on streaming video using web camera. Below is the scenarios where I am facing problem when attaching camera at runtime:
1) Application is launched without camera, and after sometime when I attach camera and trying to redetect the camera programatically, I can see the name of the attached camera sometime, which is not consistent behaviour.
2) I lanched application with camera attached to the system, I can see the names of camera, but when I try to detach the camera and re-attach the camera It's not working eventhough name of the camera after detach and re-attach I can see, which is also insonsistent behaviour.
So, please help me out in solving the above issue, if any API through which I can detect when camera is attached and detached at runtime and can work fine, with that.
Thanks.
Nitesh Kumar

Similar Messages

Sporadic error "camera disconnected or off"

I have just purchased a Mac Pro and am going crazy trying to digitize footage (which is ironic since the simplicity of the Mac was the reason I wanted to convert from PC).
Here's the deal. Before I purchased, I went to the Apple store with my camera, a Panasonic PV-GS120 to test. Footage imported easily into iMovie on an iMac. Convinced, I ordered the MacPro online. It arrived and I couldn't get it to digitize footage with same camera (same tape, wire). When I connect the camera, I keep getting the error "camera disconnected or off" even though I've tried several different cables (including brand new Mac firewire cable) and every combination and order of turning off/on computer & camera. Camera is always in correct play mode. Randomly (it seems) it worked once and never again. Sometimes the blue screen pops up and says the error, other times blue screen doesn't even show up.
Please please help - I bought this Mac to make my life easier and so far I've wasted two days and am getting nowhere (oh yeah Apple support was NO help - said our camera wasn'ts supported then sent us a list which said it was).
Michele

Nice try - just using ac power.
Update: we discovered that the rear firewire works always when we power everything off, connect everything, turn on. Front one is random - we've only got it to work once.
Meanwhile after 1 1/2 hours on the phone with Apple Tech support (no exageration) we still don't know what's wrong but they suggested we either exchange the computer or get service (probably to replace the motherboard). Apparently we can't even just return it b/c it was 'customized'. So regardless, we're stuck eith it.
So far a very disappointing and frustrating first three days as a Mac owner, to say the least.
Michele

Final cut pro not reading camera or mini dv player

My mini dv player jammed so we went to the canon gl2 to use as our vtr and final cut pro won't read it we tried our other gl2 and final cut won't read it we also tried to see if I movie would read the cameras or the machine and I movie would'nt recognize them either. Once I movie recognized the camera but would not control it or by running the camera manually. what happens when the fire wire cord is plugged in the program won't initialize. Any ideas?

Stream of consciousness writing went out with Jack Kerouac. Please use paragraphs.
What computer do you have?
Are you connecting your camera through external firewire drives?
The inability of cameras to easily connect via firewire comes up here daily, if not hourly. (facility with the SEARCH function located in the upper right of the forum is highly encouraged.) Canon cameras seem to bring their own special problems as well. If you have an iSight G5, you may have other issues ...
Try this as a troubleshooting sequence -
- Turn everything off
- If you have an external firewire drive, disconnect it.
- With only the Canon connected to the firewire bus, turn the camera on
- Turn on the Computer
- Open up System Profiler and look for the FIREWIRE section.
- Do you see your camera listed?
If no,
- you have basic connection issues - try the firewire port reset (do a search here on the forum)
- if you have an iSight camera - disconnect it and try again.
If yes,
- Open up iMovie and try to capture a short segement.
- Did it work?
if no,
- there is something potentially wacky with your camera settings.
if yes,
- Now open up FCP, make sure your firewire communication protocol is FIREWIRE BASIC
- Try to log a short clip and capture using Batch Capture.
- Did it work?
If no,
- you likely likely need to reinstall Quicktime. Search for 'quicktime reinstall' on this forum.
If yes,
- you may need to install a second bus for your capture drive. You do not want to be capturing to the system drive.
x

Did digital camera screw up iSight?

I was helping my friend attach her new digital camera to her Mac (used the USB port on the keyboard of her iMacG5), and while we successfully opened and downloaded into iPhoto, her PhotoBooth and iChat no longer showed a camera available.
We unplugged the digital camera, but continued to receive the message: installed camera is in use in another application (or something like that). We restarted, no change; shut down, no change.
What do you think happened, and how can we fix it? And I promise not to play tech support anymore.
Thanks!

Hello Elaine Soloway
Did you friend eject (click once on the camera's memory card icon on the desktop to select it and use the Finder > File > Eject menu command) before disconnecting? Not doing so can cause various problems, including ones like hers.
Restarting her Mac should have fixed the problem. Try it again with her digital camera disconnected. If the problem is still there, she should try all suggestions relevant to her system from Apple's How to Troubleshoot iSight.
Please let us know how it goes.
Cheers,
EZ Jim
PowerBook 1.67 GHz w/Mac OS X (10.4.11) G5 DP 1.8 w/Mac OS X (10.5.2) External iSight

PSE 10 Runtime error

Photoshop Elements 10 working fine but suddenly came up with Runtime error saying the 'application had requested the Runtime to terminate it in an unusual way'. Suggests 'contact the applications support team for more information'. Can anyone help?
(thread title edited by forum host)

If you are facing the issue on the editor try to reset the prefernces of the editor.
To do so, close PSE first if its open and before relaunching
Hold down the Alt + Ctrl + Shift(Windows) Opt + Cmd + Shift(Mac) keys as you click on the icon to open Elements. When asked if you want to delete the settings file, say yes.
Reset the preferences as above.
Close Elements and Relaunch it again.
Check is the error coming again or not.
-Harshit yadav

Need help with foscam cameras connecting to AirPort Extreme N

Greetings,
I could really use some help from the AirPort gurus! I have an AirPort Extreme N base station, with firmware 7.4.2. I purchased a couple of Foscam FI8908W pan and tilt cameras. I am trying to get them to work on my home network, but cannot figure it out. Personally I think it might have something to do with port forwarding, but hec I just don't know. I have tried searching for answers, but came up empty. Here is a copy of the manual for anyone if interested <http://idisk.mac.com/wheelchairguy-Public>. I have been using VMware with XP to try and setup the camera, but the camera is not found with the IP Cam setup software. I thought I might be able to directly connect to my computer with an Ethernet cable, but no go there either. Also no go with an ethernet cable plugged to the camera into the base station. I just have no idea where or what I am doing wrong. If anyone can help me, I would be very grateful.
Thanks,
Mark

Hi OneCog,
We're also have broadband connected to TimeWarner. When I first got the camera I tried the same thing and had the same problem. I never read the docs and assume plug and play. So I just plugged the ethernet cable from my laptop to the camera directly and of course my laptop was connected wirelessly to the internet. It doesn't work that easily and don't worry about the cable modem, you never have to touch it's settings.
I went to the http://foscam.us website and found these instructions that actually worked:
Foscam IP Camera Instructions
Software Insallation:
Install from the Cd the IPCamSetup.exe file OR
Or download the IPcamsetup.exe file from the website Foscam.us
a) Go to the website Foscam.us
b) Click the tool & support section (top middle section)
c) Click on Download IP Camera Tools (for FI8908W or FI8904W)
d) Click on IPCamSetup.rar (bottom left corner)
e) Click on IPCamSetup.exe
You should now have an IP Camera Tools Icon
Hardware Installation:
Plug the Ethernet network cable(grey wire) into the camera then into the router
Plug the power adapter (black wire)into the camera and then into the power outlet
Opening the Camera:
Once` plugged in correctly, double click on the icon IP Camera Tools
The Camera’s IP address will appear, double click on it to open the camera
(If “subnet doesn’t match” appears , double click on it and check the box ’Obtain IP from DHCP server’ then click on OK)
Login to the Camera:
User: admin
Password: (leave it blank)
Click Login button
NOTE: Press the first Login button if using internet Explorer or other browsers OR
Press the second Login button if using Firefox, o r Google Chrome
Test to see if working:
Click on “Live Video”
Connecting Camera to Wireless:
Type your router Ip address unto your browser( press enter)
(Don’t know your router IP address? SEE: Finding your router IP address)
You may have to login or give your password. Do so.
Under the word Wireless(on left) find ‘Channel and SSID’
Click on ‘Channel and SSID’ write down(on paper) the SSID name
Click on ‘Security” and write down Security type, Authentication, Encryption Technique and Pre-shared Key information
Login back to the camera
Double click on Ip camera tools
Double click on camera’s Ip address
User: admin
Password: ( leave blank)
Click the correct Login button for your browser
Click on ‘Device Management’or ‘For Administrator’
Click on ‘Wireless Lan Settings’
Type in your SSID, Authentication Encryption technique and Pre-shared key info that you wrote down
Press Submit
Then wait 30 seconds
Disconnect ethernnet network cable from the camera
Disconnect the power plug from the camera
Reconnect the power plug to the camera ( do not reconnect the network cable wire)
wait till camera stops moving
Login back to the camera
a)Double click on Ip camera tools
b)Double click on camera’s Ip address
c)User: admin
d)Password: ( leave blank)
e)Click the correct Login button for your browser
15. Chec k to see if camera is working by clicking on to ‘Live video’
Connecting your Camera to the Internet
Write down the local IP address of your camera
(To find this address open IP Camera Tools)( it will display the IP address of the camera as htpp://[YourCamerasLocalIPAddress])
Write down your router’s external internet IP address
( The easiest way to find this would be to Google “What is my IP address” and go to the first link which pops up and that is usually whatismyipaddress.com)
Log in to your wireless router
To do this you must enter the IP address of your router into your browser(enter)
and then enter the username and password when prompted.
( If you are unsure of the ip address or username and password of your router, SEE Finding your Router IP Address )
Directing incoming connections on your external IP address to your cameras local IP address
a)Go through the options( on left side) find ‘DMZ’
b)Click on DMZ
c)set the DMZ IP address (also called “private”/”local” IP address”) to your cameras
local IP address(by changing the last component of the number to the last or last
two digits of your cameras IP address)
d)Select enable option
e)Save by clicking ‘Apply Changes’
OR If you have more than one camera
a)click on “Virtual Server” or “Port Forwarding”
b) set the inbound port to 80 and the outbound port to 80
c) Save by clicking ‘Apply Changes’
Test it to see if you set it up correctly
open a browser and enter your external internet ip address into the address bar and press enter
You should arrive at your camera’s login screen if you successfully connected the camera to the internet
NOTE: Please keep in mind that the camera’s IP address and the Internet’s external IP address can change at any time. Check and make sure that the IP addresses haven’t changed. If they have changed, use the new IP addresses.
Finding Your Routers IP Address: (Internal)
Refer to your router’s manual OR
Retrieve your Routers Ip Address from Ip Camera Tool software
Double Click on your IP Camera Tool Icon
Then left click once on your Camera’s IP address
Right click on it and choose ‘Network Configuration’
The ‘Gateway’ number is your router Ip address ( write it down) OR
view a list of default router IP addresses, usernames and passwords
by Google searching “default router IP addresses”
and clicking on the PDF titled “List of default Router Admin Passwords and Default Router IP” at: http://www.answersthatwork.com/DownloadArea/ATW_Library/Networking/Network__4-List_of_default_Router_Admin_Passwords_an d_IPaddresses.pdf
Go to ‘find’ and type in the brand name of your router (press enter)
Write down your routers IP address
Message was edited by: dollarbrand

Anyone using PC sync on EOS Rebel cameras?

I need a PC flash sync output on my T5i. I have a hot shoe adapter but it does not work.
Anyone using a PC jack with no other flash connected?
Se my related post for details of my problem.

Hi TopDrifter,
To connect your camera to a Windows 7 computer, you'll need to change the communication mode.
To set your camera up for this, please do the following:
With the camera disconnected from the computer, turn the camera on. Press the "Menu" button. Now select the [Wrench, Hammer, 2] tab. Scroll down to "Communication" and press the "Set" button.
Select the [Print/PTP] and press "Set". This process is more completely described (and illustrated too!) on page 121 of your Digital Rebel XT Instruction Manual.
Now connect your camera to your computer and turn the camera on. Your computer should now recognize and have access to your Digital Rebel XT.
Unfortunately, Canon software cannot communicate with the Rebel XT when operating in this mode.
You may download your pictures using Windows Photo Gallery, or you may use a card reader to download images. If you haven't already done so, you may retrieve and install this program from Microsoft's download.live.com.
Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

USB CAMERA DISCONECCTED.....

So i pay a FORTUNE for a new TV with Skype... then i discover i have to pay over £100 for a Camera for it.. however it takes a day to come so i buy one...
THEN someone tells me there no stock... i wait... AND NOW I HAVE ONE
at last yeaaayyy....... SHORT LIVED EUPHORIA!...
ITS NOT FFF'N WORKIN i get the error message USB Camera Disconeccted and the Light on the camera is Dull but NEVER goes off.. iahev tried BOTH USB ports and Checked them with a flash drive to make sure they work..... NOTHING!!!! now i sit and cry whist awaiting a replay from someone on here
Sniff Sniff
Ben

HI
I have same problem also on my UE46D8005 and talk-7180
Say "USB Camera Disconnected" Blink sometimes when i take it out
and write connecting... somthing more i cant see
you get some suport ??

Strange camera problem when adjusting screen?

I just bought an S10 and noticed that the camera disconnects then reconnects every time I move the screen forward or backward.
Everytime this happens I hear the Windows chime indicating that a USB device was unplugged then plugged back in.
Is this normal?

This looks like some wire lost it's seat or has defect in it. You should send it to repair.
//help will save the world

The air app cannot detect the new added camera

i made a desktop air-app. the problem is when i unpluged my usb camera and start the air app . the app detect the existed cameras with Camera.names.length = 2; and then i pluged another usb camera and use the Camera.names.length to detect the new camera, but the result is still 2 , not the 2 existed camera with the new added one which the total is 3. then i close the air-app and start it again ,this time the camera.names.length is 3. why ? the air-app just cannot detect the new added camera? the only way the air-app can detect the new added camera is restart the app?

Air ow flash player for that matter won't detect camera added at runtime. It will detect if you remove the camera while you were capturing images from the camera. You can try to scan for camera suing a timer and see if it detects it then.
There is also a not so documented flash.media.scanHardware() method, which should force a hardware scan. I did not used it yet so can't vouch for it.

Lync 2013 A/V Conference meeting with Logitech BCC950 conference cam auto sense not working

Hello All,
I have Lync 2013 server's configured & everything is working fine. We are doing the A/V Conference meeting by connecting Logitech BCC950 conference cam.
Logitech conferencecam connected in the conference rooms. Now on one user laptop we have connected this logitech cam to the laptop & meeting is started, below below issues are:
1) In the middle of the meeting device getting automatically disconnected. Tried to manually select the Integrated WebCam but it's not getting detected.
2) Whenever we connect this Logitech cam it should get automatically selected as default device in Lync 2013 client which is not happnening.
3) If the Logitech cam disconnect it should get detected Inbuilt Web Cam
Can someone help us to resolve this issue.
Any help really appreciated
Thanks & Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

Hello Logimg1,
Thanks for your reply & we have checked below options:
1) In the middle of the meeting device getting automatically disconnected. Tried to manually select the Integrated WebCam but it's not getting detected.
LogiMG> I have not experienced this issue, but could you tell me if the Blue LED in the camera is lit when you experience this disconnect? It is strange that you can't switch to the Integrated camera.
Anand : Cusotmer faced this issue by I tried to reproduce but I haven't faced this issue.
2) Whenever we connect this Logitech cam it should get automatically selected as default device in Lync 2013 client which is not happnening.
LogiMG> Lync remembers the last camera selected and the OK button is pressed. If you use the 'X' it will not be remembered. What are the behaviors of the camera at this point? Do you see it go through the connection sequence?
Anand : First time we need to make as a default device as well as default communication device under Control Panel sound options.
3) If the Logitech cam disconnect it should get detected Inbuilt Web Cam
LogiMG> What is the state of the LED for either camera? If it is on, then the camera(s) is streaming video.
Anand : Customers laptop faced this issue, but when I was tried it's selecting Inbuilt Cam
Thanks
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

Runtime exec IOException issues

Hello,
I have spent two 10 hours days on this problem with countless search permutations and peering into everything from kernel source to java source. Unfortunately, I am not coming up with useful results.
Overview:
I have a very large java application (Apache solr) running on a server with 12GB memory. Without going into too much detail, this application at a point will use a Runtime exec call to fire off a bash shell script. Over time, however, I end up with an IOException "Cannot allocate memory." (More info and stack trace below.)
That application aside I have been able to reproduce this by varying the -Xms and -Xmx jvm parameters with confusing results using the simple program below:
//Use with various -Xms and -Xmx arguments to produce
//IOException on call to Runtime.exec()
import java.io.*;
public class DoRuntime {
   public static void main(String args[]) throws IOException {
      Runtime runtime = Runtime.getRuntime();
      long total = runtime.totalMemory();
      long max = runtime.maxMemory();
      long free = runtime.freeMemory();
      System.out.println("total: " + total);
      System.out.println("max: " + max);
      System.out.println("free: " + free);
      Process process = runtime.exec("/bin/ls");
      InputStream is = process.getInputStream();
      InputStreamReader isr = new InputStreamReader(is);
      BufferedReader br = new BufferedReader(isr);
      String line;
      while ((line = br.readLine()) != null) {
         System.out.println(line);
}Here are some sample runs:
RUN1
rwoodrum@util1wad:~/tmp$ java DoRuntime
total: 188743680
max: 954466304
free: 187759312
DoRuntime.class
DoRuntime.java
rwoodrum@util1wad:~/tmp$
RUN2
rwoodrum@util1wad:~/tmp$ java -Xms10g -Xmx10g DoRuntime
total: 10290069504
max: 10290069504
free: 10236381080
Exception in thread "main" java.io.IOException: java.io.IOException: Cannot allocate memory
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
        at java.lang.ProcessImpl.start(ProcessImpl.java:65)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
        at java.lang.Runtime.exec(Runtime.java:591)
        at java.lang.Runtime.exec(Runtime.java:429)
        at java.lang.Runtime.exec(Runtime.java:326)
        at DoRuntime.main(DoRuntime.java:14)
rwoodrum@util1wad:~/tmp$
RUN3
rwoodrum@util1wad:~/tmp$ java -Xms10g -Xmx11g DoRuntime
total: 10290069504
max: 10498867200
free: 10236381080
DoRuntime.class
DoRuntime.java
rwoodrum@util1wad:~/tmp$-----
(FWIW, I get the same results replacing /bin/ls with something as lightweight as /bin/true.)
As can be seen in the above output of RUN2, I have set a fixed heap size of 10GB. The jvm seems content with that heap size, but when it goes to exec the child process it becomes rather unhappy. From this I would perhaps conclude that ultimately inside the call to forkAndExec (libjava.so) the call to fork() failed with an ENOMEM. (As a side note, an strace on the process doesn't actually ever show a fork, only a call to clone - which utilizes a fork eventually - more on clone below.)
The results of RUN3, however, seem to imply that the problem is within the jvm itself. In RUN3, I set the initial heap allocation to 10GB, as in RUN2, but I set the maximum at 11GB. One would think (or at least I would) that if the fork in RUN2 failed that it would certainly fail in the case of RUN3. It doesn't.
The manpage of clone indicates that the child process will "share parts of its execution context with the calling process". Indeed, if I'm reading it correctly, it indicates that the child process stack (among other things) is housed in the parent process address space.
Could it be that by setting this very large, fixed heap size as in RUN2, there is no room for the jvm to "maneuver" and properly handle the effort of the Runtime.exec? The fact that RUN3 is successful is what has made me think something like this, but I am by far an expert on how the jvm would handle that sort of thing.
In our production setup of this application, I adjusted the Xmx setting to be something larger than the Xms setting. This worked for a period of time, but eventually produced the same results. I suspect over time the heap simply increased toward the max and again the jvm couldn't do its thing when it came time to RunTime.exec. The fact that this happens on the trivial Runtime.exec program would seem to rule out a memory leak of the production application.
Ultimately something fishy is going on with memory, but with seemingly contradictory results, I am at a loss of where the problem lies.
If I have omittied any potentially relevant information, please let me know. Any thoughts are greatly appreciated.
Some basic system information:
rwoodrum@util1wad:~/tmp$ free
             total       used       free     shared    buffers     cached
Mem:      12304936   12200376     104560          0     337276    7082508
-/+ buffers/cache:    4780592    7524344
Swap:      2097144         32    2097112
rwoodrum@util1wad:~/tmp$ uname -a
Linux util1wad 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 GNU/Linux
rwoodrum@util1wad:~/tmp$ java -version
java version "1.5.0_10"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_10-b03, mixed mode)-ryan woodrum

I've continued to investigate this with my discoveries below. I've found some more interesting nuances, but am still not satisfied with the explanation of what is going on here. For time reasons, I've capitulated to a somewhat lame workaround.
The test run in the 1.6.0 jvm environment is somewhat revealing in that it confirms that the eventual call to fork (I'm kind of guessing it's the fork call here) is returning an ENOMEM. The 1.5.0 jvm was not returning the actual errno from the call in the JNI code. Checking out $linux_src/include/asm-generic/errno-base.h indeed enumerates ENOMEM to 12.
When I saw this, I started looking at the memory commit inside of /proc/meminfo to see what was going on when I would launch the jvm with the varying Xmx and Xms parameters. Somewhat unsurprisingly at this point, when I would run with large a large heap, the Committed_AS would skyrocket by a proportion roughly equal to the fixed heap size. (See here http://lwn.net/Articles/28345/ for an definition of Committed_AS and other /proc/meminfo fields.)
With the above information in hand, I wanted to confirm without a doubt that the kernel was the thorn in my side. So on a test system I started to play around with the vm_overcommit feature - see $linux_src/Documentation/vm/overcommit-accounting for definitions of modes 0,1, and 2). Sure enough, toying with these modes I was able to alter the behavior of launching the jvm. I switched from the default heuristic mode (0) to an "always overcommit" mode and it would launch and sucessfully fork and exec every time. No surprise there.
What IS surprising, however, is that if, under the default heuristic mode, I specify the jvm parameters differently it will sucessfully run and fork and exec the subprocess. It seems odd to me that at the OS level, specifying `java -Xms4g -Xmx4g` will cause the subprocess fork to fail but specifying `java -Xms4g -Xmx5g` will NOT cause the fork to fail. Running with the latter parameters shows the exact same Committed_AS spike. This all begs the question(s): What's the difference? With a min heap size set to 4g (or whatever) on the both jvm runs, how does a jvm parameter (especially one that allows MORE growth of the heap) impact this call to fork? One variable in the picture at this point that I'm unsure of is the strace call to clone(). I don't know what this could be doing to make things behave differently.
So as I noted, above, I have a relatively lame workaround. Blindly add more swap to increase the CommittedLimit inside the kernel. It'll never get used, it's a waste of space, and, perhaps most importantly, on principal it just rubs me the wrong way.
-ryan woodrum

My thoughts, ?s, experiences with my new zvm:60 after having a 30gb for 5hrs pr

This is my first post here. I am a forum user so Ill try not to be a troll. I did get done pouring over the threads here for hrs too.
So I went shopping for my first media player a while ago. I read all the reviews I could on every player known to man (CC is a great retail web site to get reviews and the bay). Well the Zen:M seemed to take the cake as the best player for a demanding seasoned tech user. And really just plain over all.
So I bought a 30gb player from a private online seller (you can guess) and after getting it up and running found all the reviews to be true. Infact I even loved it more than I anticipated. However my experience was cut short. I had finished using the player, turned it off (it fully shut itself down), placed it in my coat pocket and draped the coat over a chair when it suddenly fell out of my coat onto a hard wood floor. Now the unit was in a thin silicon skin and could not have fallen more than 2ft (more like ft) and that was all folks. Dead as a door nail. No power up, no ?help me? when connected to the comp, no rest button, nothing. All it did when connected was flash the power/hold button charge light abnormally fast with a clicking sound? Huh? I think the battery somehow came disconnected. ?To anyone reading this, are all these fine players this sensiti've to vibration? Yeah I know its a HD player, and no one wants to see their player dropped, so is this the norm?
Which brings me to my new ZVM60. Love it. The only difference I notice, other than the size (getting to that) is it seems the touch sensor is slightly more sensiti've. Great, I like that! Now the size. It should be noted that as of now this 60gb player is WIDELY mis-documented as being the same size as the 30gb. Infact a well known web retailer I bought this from is a culprit of this also. I also bought an extended 2 yr warrantee after this past incident. However Im having a real hard time finding a skin or case for it. The leather one doesnt appeal to me sorry. I searched the threads here and am finding nothing. Anything new come around since? Id love to get a ToughSkin for it but am not holding my breath. I dont mind having a player that by all standards is a TANK. Just let me protect my tank. On that note, anyone know why the 60gb is bigger? I thought all PCMCIA HDs were the same size.
Lastly, Im using this player with a properly maintained XP computer with WMP0. I rip all my store bought CDs at 28 in WMA. This and some ripped vinyl is how the player is primarily used. Am I missing anything? Also the player has firmware ver .0.04 , is it worth updating? Im kinda leary to update having been around BIOS flashing nightmares back in the day. Will I loose all my data doing a firm update? Also, I dont know if anyone out there is doing this but I heard the newer Alpine car stereos can work with a bare bone external HD filled with audio files. I got that info from a few reliable sources. Anyone doing this and know what file format these heads are compatible with? Id rather not have to keep my Zen in the car if I dont have to risk it. Also any takes on how Im doing things here are more than welcome.
So in conclusion I love my Zen. Id simply like a good skin to protect it with?? The GF has a coughPOD video, will see what she thinks of this not so little guy. Also will keep all up to date on any findings I have. Please do the same.
Dave

I will check out the web site. On that note thanks for it. However, as stated in the thread, the 60gb, EVER SO SAD, is a bit thicker than the 30gb. Im really praying some skins come out. Ive been playing with this player all night long. ON THAT NOTE, people complaining and having issues with the bass. I know where you are coming from. However a semi solution can be had with playing with the vol limiter in combo with the bass boost func and the custom EQ. Im sure this is no news flash to most techies out there. However being an audiofool (aka audiophile) and knowing a little about the hardware involved in all this. I have a really bad feeling, and bad track record of being right on this when Id rather not be, that this is infact an OP-AMP issue and power dedication issue too the afore mentioned. Firmware or not, you play with bass boost and EQ and there is no way to get this player to dedicate enough KICK, as its been termed here, to the headphones without distortion. I think this may be WHY there hasnt been a working firmware fix to this issue. I think some may not realize, as the old analogy goes, a chain is only as stong as its weakest link, and I have a BAD feeling that the OP-AMP is that link holding this fine player back. No bad feeling to those in the design depo. I know how cost concerns go and who those who dont know JACK dictate construction. Im sure you all tried your hardest to design the best player on the market. You suceeded in all regard IMO. Creative may be making some SERIOUS mistakes by not properly supporting their prodigy birth but dont give up on designing some killer players for us who do notice and infact buy. We buyers who do infact know and buy what is really best rely on you R&D and Designers out there, who I hope somehow read these threads, or get a heads up now and then, that we praise you and thank you for doing what no others out there do, by designing a player that really does meet the expections of the small market that has a brain and appreciates what you do. A small thanx to those that really matter. Keep up the good work! You do infact matter in an age where real genius gets overlooked. Dave?

7410 can't scan wirelessly

Installed the full version, over the network on my 7410 - printing works fine on Win XP. It doesn't appear that the scanner driver is installed - as the HP digital imaging monitor shows the device as disconnected.
What I've done.
1.installed with official HP release on their web site
2.uninstalled/reinstalled many times - the wireless printing always works
2a. uninstalled each component using the windows control panel add/remove programs
2b. uninstalled using the HP level 3 .bat file contained on the distrubtion located in utils/ccc
3. on installation, the install seems to bog down at the 96% mark for quite a while - but will always finish
4. I get a bunch of install failed messages in my setupapi.log - see below
[SetupAPI Log]
OS Version = 5.1.2600 Service Pack 3
Platform ID = 2 (NT)
Service Pack = 3.0
Suite = 0x0100
Product Type = 1
Architecture = x86
[2012/01/03 18:28:50 628.3 Driver Install]
#-019 Searching for hardware ID(s): vid_03f0&pid_4311&ip_scan
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.
[2012/01/03 18:29:09 3660.2]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{C6029209-C434-4B64-B6F2-74987DC8E3D2}
#I060 Set selected driver.
#-019 Searching for hardware ID(s): vid_03f0&pid_4311&ip_scan
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.
[2012/01/03 18:48:31 3496.3]
#-198 Command line processed: "C:\Documents and Settings\AJS\Desktop\HP7410_full\Setup\hpzprl01.exe" -m preloadproductdrivers -ll enu,esn,fra,ptb,enu,ell,plk,rus,trk,chs,cht,csy,dan,deu,esn,fin,fra,hun,ita,jpn,kor,nld,nob,ptb,sve -l ENU -f C:\WINDOWS\hpoins05.dat -Validate No -w 131554
#W389 No [STRINGS.0409] or [STRINGS.0009] section in C:\Program Files\HP\Digital Imaging\{342C7C88-D335-4bc2-8CF1-281857629CE2}\hposcu08.inf, using [STRINGS] instead.
[2012/01/03 18:48:29 3496.1]
#-198 Command line processed: "C:\Documents and Settings\AJS\Desktop\HP7410_full\Setup\hpzprl01.exe" -m preloadproductdrivers -ll enu,esn,fra,ptb,enu,ell,plk,rus,trk,chs,cht,csy,dan,deu,esn,fin,fra,hun,ita,jpn,kor,nld,nob,ptb,sve -l ENU -f C:\WINDOWS\hpoins05.dat -Validate No -w 131554
#W389 No [STRINGS.0409] or [STRINGS.0009] section in C:\Program Files\HP\Digital Imaging\{342C7C88-D335-4bc2-8CF1-281857629CE2}\hposcu08.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in C:\WINDOWS\INF\oem27.inf, using [STRINGS] instead.
[2012/01/03 18:49:40 3068.1]
#-199 Executing "C:\Documents and Settings\AJS\Desktop\HP7410_full\Setup\hponiscan01.exe" with command line: hponiscan01.exe -f "C:\Documents and Settings\AJS\Desktop\HP7410_full\setup\..\hposcu08.inf" -m "VID_03F0&Pid_4311&IP_SCAN" -a 192.168.0.2 -e 0018715BD88F -n 1
#W389 No [STRINGS.0409] or [STRINGS.0009] section in C:\Documents and Settings\AJS\Desktop\HP7410_full\hposcu08.inf, using [STRINGS] instead.
[2012/01/03 18:49:40 3068.132]
#-199 Executing "C:\Documents and Settings\AJS\Desktop\HP7410_full\Setup\hponiscan01.exe" with command line: hponiscan01.exe -f "C:\Documents and Settings\AJS\Desktop\HP7410_full\setup\..\hposcu08.inf" -m "VID_03F0&Pid_4311&IP_SCAN" -a 192.168.0.2 -e 0018715BD88F -n 1
#I060 Set selected driver.
#-019 Searching for hardware ID(s): vid_03f0&pid_4311&ip_scan
#W389 No [STRINGS.0409] or [STRINGS.0009] section in c:\documents and settings\ajs\desktop\hp7410_full\hposcu08.inf, using [STRINGS] instead.
#I022 Found "VID_03F0&Pid_4311&IP_SCAN" in c:\documents and settings\ajs\desktop\hp7410_full\hposcu08.inf; Device: "HP Officejet 7400 series"; Driver: "HP Officejet 7400 series"; Provider: "Hewlett-Packard"; Mfg: "Hewlett-Packard"; Section name: "PSC.Net.NTWIA".
#I023 Actual install section: [PSC.Net.NTWIA]. Rank: 0x00000000. Effective driver date: 10/23/2002.
#-019 Searching for hardware ID(s): vid_03f0&pid_4311&ip_scan
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [PSC.Net.NTWIA] in "c:\documents and settings\ajs\desktop\hp7410_full\hposcu08.inf".
#I320 Class GUID of device remains: {6BDD1FC6-810F-11D0-BEC7-08002BE2092F}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
[2012/01/03 18:49:41 3068.134]
#-199 Executing "C:\Documents and Settings\AJS\Desktop\HP7410_full\Setup\hponiscan01.exe" with command line: hponiscan01.exe -f "C:\Documents and Settings\AJS\Desktop\HP7410_full\setup\..\hposcu08.inf" -m "VID_03F0&Pid_4311&IP_SCAN" -a 192.168.0.2 -e 0018715BD88F -n 1
#W389 No [STRINGS.0409] or [STRINGS.0009] section in c:\documents and settings\ajs\desktop\hp7410_full\hposcu08.inf, using [STRINGS] instead.
[2012/01/03 18:49:41 3068.135]
#-199 Executing "C:\Documents and Settings\AJS\Desktop\HP7410_full\Setup\hponiscan01.exe" with command line: hponiscan01.exe -f "C:\Documents and Settings\AJS\Desktop\HP7410_full\setup\..\hposcu08.inf" -m "VID_03F0&Pid_4311&IP_SCAN" -a 192.168.0.2 -e 0018715BD88F -n 1
#W389 No [STRINGS.0409] or [STRINGS.0009] section in c:\documents and settings\ajs\desktop\hp7410_full\hposcu08.inf, using [STRINGS] instead.
#I140 Installing device class: "Image" {6bdd1fc6-810f-11d0-bec7-08002be2092f}.
#E067 Could not locate section [ClassInstall32].
#E142 Class: {6BDD1FC6-810F-11D0-BEC7-08002BE2092F}. Install failed. Error 0xe0000101: The required section was not found in the INF.
[2012/01/03 19:04:53 3460.3]
#-198 Command line processed: "C:\Documents and Settings\AJS\Desktop\HP7410_full\Setup\hpzprl01.exe" -inf -m preloadproductdrivers -l ENU -f C:\WINDOWS\hpoins05.dat -Validate No -w 131554
#W389 No [STRINGS.0409] or [STRINGS.0009] section in C:\Program Files\HP\Digital Imaging\{342C7C88-D335-4bc2-8CF1-281857629CE2}\hposcu08.inf, using [STRINGS] instead.
[2012/01/03 19:04:52 3460.1]
#-198 Command line processed: "C:\Documents and Settings\AJS\Desktop\HP7410_full\Setup\hpzprl01.exe" -inf -m preloadproductdrivers -l ENU -f C:\WINDOWS\hpoins05.dat -Validate No -w 131554
#W389 No [STRINGS.0409] or [STRINGS.0009] section in C:\Program Files\HP\Digital Imaging\{342C7C88-D335-4bc2-8CF1-281857629CE2}\hposcu08.inf, using [STRINGS] instead.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in C:\WINDOWS\INF\oem27.inf, using [STRINGS] instead.
Obsevations
1.when trying to install, I've always had to kill the wrapper.exe process to coax it to proceed (is this normal?)
Bottom line - can anyone help me out?
p.s. Other things I've tried
1. swung dead chicken bones and chanted heavily and vociferously - and with gusto.
2. said many prayers - i tried all of the known deities to no avail.
3. employed the hp motto "think" - also to no avail.
3. loaded my 12 guage and pointed it at the printer - I guess idle threats didn't work, but it was worth a shot (no pun intended)

Ok, I think I've solved this difficult issue. There was a couple of missing parent keys. Try adding this to your registry. I had noticed the missing keys by comparing to a 'healthy' machine. I think the uninstall level 4 may be the culprit. The keys have to do with where imaging devices are parked. Once added, not only did my scanner work wirelessly, but the install went all the way through without stalling at 96% and also fixed another issue with my "Add a scanner" not working. Please ignore my Canon A60 and Intel microscope in the entries. Just copy the keys and import. Copy carefully from the below - there are 2 keys - look for --KEY--- and ---KEY2---
---KEY1---
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}]
"Class"="Image"
@="Imaging devices"
"Installer32"="sti_ci.dll,ClassInstall"
"TroubleShooter-0"="hcp://help/tshoot/tsInputDev.htm"
"Icon"="0"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0001]
"DevLoader"="*ntkern"
"NTMPDriver"="STVqx3.sys"
"PageOutWhenUnopened"=hex:01
"DontSuspendIfStreamsAreRunning"=hex:01
"InfPath"="oem19.inf"
"InfSection"="Camera.Device"
"InfSectionExt"=".NT"
"ProviderName"="Intel"
"DriverDateData"=hex:00,80,56,84,e3,c2,c0,01
"DriverDate"="4-12-2001"
"DriverVersion"="1.10.18.0"
"MatchingDeviceId"="usb\\vid_0813&pid_0001"
"DriverDesc"="Intel Play QX3 Microscope"
"Vendor"="Intel"
"FriendlyName"="Intel Play QX3 Microscope"
"DeviceID"="{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\\0001"
"Capabilities"=dword:00000000
"DeviceType"=dword:00000000
"DeviceSubType"=dword:00000000
"IsPnP"=dword:00000001
"Camera Name"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00
"Brightness"=hex:94,11,00,00,02,00,00,00,02,00,00,00
"Contrast"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Saturation"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Last Image Size"=hex:40,01,00,00,f0,00,00,00
"Compression"=hex:00
"VFFOV Control"=hex:00
"Sensor Rate"=hex:04
"50Hz Banding Filter"=hex:00
"Never Flicker"=hex:00
"Backlit"=hex:00
"Disable Banding Filter"=hex:01
"Maximum Alternate"=hex:03
"Pan/Tilt"=hex:04,00,00,00,06,00,00,00
"Zoom"=hex:00
"Colour Balance"=hex:14,05,07
"Exposure"=hex:01,00,97,01
"CompGains"=hex:dc,d6,d6,e6
"Disable AutoExposure"=hex:00
"Disable Colour Balance"=hex:01
"AEC Gain Ceiling"=hex:01
"ACB Matrix"=hex:60,e2,fe,f7,59,f0,fc,e4,60
"Enable Push Button"=hex:01
"GPIO PP Out"=hex:0f
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0002]
"DevLoader"="*ntkern"
"NTMPDriver"="STVqx3.sys"
"PageOutWhenUnopened"=hex:01
"DontSuspendIfStreamsAreRunning"=hex:01
"InfPath"="oem19.inf"
"InfSection"="Camera.Device"
"InfSectionExt"=".NT"
"ProviderName"="Intel"
"DriverDateData"=hex:00,80,56,84,e3,c2,c0,01
"DriverDate"="4-12-2001"
"DriverVersion"="1.10.18.0"
"MatchingDeviceId"="usb\\vid_0813&pid_0001"
"DriverDesc"="Intel Play QX3 Microscope"
"Vendor"="Intel"
"FriendlyName"="Intel Play QX3 Microscope #2"
"DeviceID"="{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\\0002"
"Capabilities"=dword:00000000
"DeviceType"=dword:00000000
"DeviceSubType"=dword:00000000
"IsPnP"=dword:00000001
"Camera Name"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00
"Brightness"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Contrast"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Saturation"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Last Image Size"=hex:40,01,00,00,f0,00,00,00
"Compression"=hex:00
"VFFOV Control"=hex:00
"Sensor Rate"=hex:04
"50Hz Banding Filter"=hex:00
"Never Flicker"=hex:00
"Backlit"=hex:00
"Disable Banding Filter"=hex:01
"Maximum Alternate"=hex:03
"Pan/Tilt"=hex:04,00,00,00,06,00,00,00
"Zoom"=hex:00
"Colour Balance"=hex:14,05,07
"Exposure"=hex:01,00,97,01
"CompGains"=hex:dc,d6,d6,e6
"Disable AutoExposure"=hex:00
"Disable Colour Balance"=hex:01
"AEC Gain Ceiling"=hex:01
"ACB Matrix"=hex:60,e2,fe,f7,59,f0,fc,e4,60
"Enable Push Button"=hex:01
"GPIO PP Out"=hex:0f
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0003]
"DevLoader"="*ntkern"
"NTMPDriver"="STVqx3.sys"
"PageOutWhenUnopened"=hex:01
"DontSuspendIfStreamsAreRunning"=hex:01
"InfPath"="oem19.inf"
"InfSection"="Camera.Device"
"InfSectionExt"=".NT"
"ProviderName"="Intel"
"DriverDateData"=hex:00,80,56,84,e3,c2,c0,01
"DriverDate"="4-12-2001"
"DriverVersion"="1.10.18.0"
"MatchingDeviceId"="usb\\vid_0813&pid_0001"
"DriverDesc"="Intel Play QX3 Microscope"
"Vendor"="Intel"
"FriendlyName"="Intel Play QX3 Microscope #3"
"DeviceID"="{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\\0003"
"Capabilities"=dword:00000000
"DeviceType"=dword:00000000
"DeviceSubType"=dword:00000000
"IsPnP"=dword:00000001
"Camera Name"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00
"Brightness"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Contrast"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Saturation"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Last Image Size"=hex:60,01,00,00,20,01,00,00
"Compression"=hex:05
"VFFOV Control"=hex:00
"Sensor Rate"=hex:82
"50Hz Banding Filter"=hex:00
"Never Flicker"=hex:00
"Backlit"=hex:00
"Disable Banding Filter"=hex:00
"Maximum Alternate"=hex:03
"Pan/Tilt"=hex:00,00,00,00,00,00,00,00
"Zoom"=hex:00
"Colour Balance"=hex:0a,0a,0a
"Exposure"=hex:00,00,8b,00
"CompGains"=hex:dc,d6,d6,e6
"Disable AutoExposure"=hex:00
"Disable Colour Balance"=hex:00
"AEC Gain Ceiling"=hex:02
"ACB Matrix"=hex:60,e0,f8,e8,60,f3,ef,e8,60
"Enable Push Button"=hex:00
"GPIO PP Out"=hex:ff
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0005]
"HardwareConfig"=hex:04
"USDClass"="{B5EE90B0-D5C5-11D2-82D5-00C04F8EC183}"
"InfPath"="ptpusb.inf"
"InfSection"="PTP"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.0"
"MatchingDeviceId"="usb\\class_06&subclass_01&prot_01"
"DriverDesc"="Canon PowerShot A60"
"CreateFileName"=""
"SubClass"="StillImage"
"Vendor"="Generic"
"FriendlyName"="Canon PowerShot A60"
"ICMProfiles"="sRGB Color Space Profile.icm"
"DeviceID"="{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\\0005"
"Capabilities"=dword:00000035
"DeviceType"=dword:00000002
"DeviceSubType"=dword:00000000
"IsPnP"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0005\DeviceData]
"Model"="PTP"
"QueryDeviceForName"=dword:00000000
"Server"="local"
"UI DLL"="sti.dll"
"UI Class ID"="{4DB1AD10-3391-11D2-9A33-00C04FA36145}"
"ICMProfile"=hex:73,00,52,00,47,00,42,00,20,00,43,00,6f,00,6c,00,6f,00,72,00,\
20,00,53,00,70,00,61,00,63,00,65,00,20,00,50,00,72,00,6f,00,66,00,69,00,6c,\
00,65,00,2e,00,69,00,63,00,6d,00,00,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0005\Events]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0005\Events\Connected]
@="Digital camera connected"
"GUID"="{A28BBADE-64B6-11d2-A231-00C04FA31809}"
"LaunchApplications"="*"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0005\Events\Disconnected]
@="Digital camera disconnected"
"GUID"="{143E4E83-6497-11d2-A231-00C04FA31809}"
"LaunchApplications"="*"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0006]
"HardwareConfig"=hex:04
"USDClass"="{B5EE90B0-D5C5-11D2-82D5-00C04F8EC183}"
"InfPath"="ptpusb.inf"
"InfSection"="PTP"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.0"
"MatchingDeviceId"="usb\\class_06&subclass_01&prot_01"
"DriverDesc"="Canon PowerShot A60"
"CreateFileName"=""
"SubClass"="StillImage"
"Vendor"="Generic"
"FriendlyName"="Canon PowerShot A60"
"ICMProfiles"="sRGB Color Space Profile.icm"
"DeviceID"="{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\\0006"
"Capabilities"=dword:00000035
"DeviceType"=dword:00000002
"DeviceSubType"=dword:00000000
"IsPnP"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0006\DeviceData]
"Model"="PTP"
"QueryDeviceForName"=dword:00000000
"Server"="local"
"UI DLL"="sti.dll"
"UI Class ID"="{4DB1AD10-3391-11D2-9A33-00C04FA36145}"
"ICMProfile"=hex:73,00,52,00,47,00,42,00,20,00,43,00,6f,00,6c,00,6f,00,72,00,\
20,00,53,00,70,00,61,00,63,00,65,00,20,00,50,00,72,00,6f,00,66,00,69,00,6c,\
00,65,00,2e,00,69,00,63,00,6d,00,00,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0006\Events]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0006\Events\Connected]
@="Digital camera connected"
"GUID"="{A28BBADE-64B6-11d2-A231-00C04FA31809}"
"LaunchApplications"="*"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0006\Events\Disconnected]
@="Digital camera disconnected"
"GUID"="{143E4E83-6497-11d2-A231-00C04FA31809}"
"LaunchApplications"="*"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0007]
"DevLoader"="*ntkern"
"NTMPDriver"="STVqx3.sys"
"PageOutWhenUnopened"=hex:01
"DontSuspendIfStreamsAreRunning"=hex:01
"InfPath"="oem19.inf"
"InfSection"="Camera.Device"
"InfSectionExt"=".NT"
"ProviderName"="Intel"
"DriverDateData"=hex:00,80,56,84,e3,c2,c0,01
"DriverDate"="4-12-2001"
"DriverVersion"="1.10.18.0"
"MatchingDeviceId"="usb\\vid_0813&pid_0001"
"DriverDesc"="Intel Play QX3 Microscope"
"Vendor"="Intel"
"FriendlyName"="Intel Play QX3 Microscope #4"
"DeviceID"="{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\\0007"
"Capabilities"=dword:00000000
"DeviceType"=dword:00000000
"DeviceSubType"=dword:00000000
"IsPnP"=dword:00000001
"Camera Name"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00
"Brightness"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Contrast"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Saturation"=hex:88,13,00,00,02,00,00,00,02,00,00,00
"Last Image Size"=hex:60,01,00,00,20,01,00,00
"Compression"=hex:05
"VFFOV Control"=hex:00
"Sensor Rate"=hex:81
"50Hz Banding Filter"=hex:00
"Never Flicker"=hex:00
"Backlit"=hex:00
"Disable Banding Filter"=hex:00
"Maximum Alternate"=hex:03
"Pan/Tilt"=hex:00,00,00,00,00,00,00,00
"Zoom"=hex:00
"Colour Balance"=hex:0a,0a,0a
"Exposure"=hex:00,00,97,00
"CompGains"=hex:dc,d6,d6,e6
"Disable AutoExposure"=hex:00
"Disable Colour Balance"=hex:00
"AEC Gain Ceiling"=hex:02
"ACB Matrix"=hex:60,e0,f8,e8,60,f3,ef,e8,60
"Enable Push Button"=hex:00
"GPIO PP Out"=hex:ff
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0008]
"HardwareConfig"=hex:04
"USDClass"="{B5EE90B0-D5C5-11D2-82D5-00C04F8EC183}"
"InfPath"="ptpusb.inf"
"InfSection"="PTP"
"ProviderName"="Microsoft"
"DriverDateData"=hex:00,80,62,c5,c0,01,c1,01
"DriverDate"="7-1-2001"
"DriverVersion"="5.1.2600.0"
"MatchingDeviceId"="usb\\class_06&subclass_01&prot_01"
"DriverDesc"="Canon PowerShot A60"
"CreateFileName"=""
"SubClass"="StillImage"
"Vendor"="Generic"
"FriendlyName"="Canon PowerShot A60"
"ICMProfiles"="sRGB Color Space Profile.icm"
"DeviceID"="{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\\0008"
"Capabilities"=dword:00000035
"DeviceType"=dword:00000002
"DeviceSubType"=dword:00000000
"IsPnP"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0008\DeviceData]
"Model"="PTP"
"QueryDeviceForName"=dword:00000000
"Server"="local"
"UI DLL"="sti.dll"
"UI Class ID"="{4DB1AD10-3391-11D2-9A33-00C04FA36145}"
"ICMProfile"=hex:73,00,52,00,47,00,42,00,20,00,43,00,6f,00,6c,00,6f,00,72,00,\
20,00,53,00,70,00,61,00,63,00,65,00,20,00,50,00,72,00,6f,00,66,00,69,00,6c,\
00,65,00,2e,00,69,00,63,00,6d,00,00,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0008\Events]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0008\Events\Connected]
@="Digital camera connected"
"GUID"="{A28BBADE-64B6-11d2-A231-00C04FA31809}"
"LaunchApplications"="*"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0008\Events\Disconnected]
@="Digital camera disconnected"
"GUID"="{143E4E83-6497-11d2-A231-00C04FA31809}"
"LaunchApplications"="*"
---KEY 2---
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#DOT4#Vid_03f0&Pid_2311&Rev_0100&SCAN#5&5714445&3&1#{6bdd1fc6-810f-11d0-bec7-08002be2092f}]
"DeviceInstance"="DOT4\\Vid_03f0&Pid_2311&Rev_0100&SCAN\\5&5714445&3&1"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#DOT4#Vid_03f0&Pid_2311&Rev_0100&SCAN#5&5714445&3&1#{6bdd1fc6-810f-11d0-bec7-08002be2092f}\#]
"SymbolicLink"="\\\\?\\DOT4#Vid_03f0&Pid_2311&Rev_0100&SCAN#5&5714445&3&1#{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#USB#Vid_03f0&Pid_4111&MI_00#5&1dc9c0b4&3&0000#{6bdd1fc6-810f-11d0-bec7-08002be2092f}]
"DeviceInstance"="USB\\Vid_03f0&Pid_4111&MI_00\\5&1dc9c0b4&3&0000"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#USB#Vid_03f0&Pid_4111&MI_00#5&1dc9c0b4&3&0000#{6bdd1fc6-810f-11d0-bec7-08002be2092f}\#]
"SymbolicLink"="\\\\?\\USB#Vid_03f0&Pid_4111&MI_00#5&1dc9c0b4&3&0000#{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#USB#Vid_04a9&Pid_3074#4&2e05fc02&0&1#{6bdd1fc6-810f-11d0-bec7-08002be2092f}]
"DeviceInstance"="USB\\Vid_04a9&Pid_3074\\4&2e05fc02&0&1"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#USB#Vid_04a9&Pid_3074#4&2e05fc02&0&1#{6bdd1fc6-810f-11d0-bec7-08002be2092f}\#]
"SymbolicLink"="\\\\?\\USB#Vid_04a9&Pid_3074#4&2e05fc02&0&1#{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#USB#Vid_04a9&Pid_3074#4&2e05fc02&0&2#{6bdd1fc6-810f-11d0-bec7-08002be2092f}]
"DeviceInstance"="USB\\Vid_04a9&Pid_3074\\4&2e05fc02&0&2"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#USB#Vid_04a9&Pid_3074#4&2e05fc02&0&2#{6bdd1fc6-810f-11d0-bec7-08002be2092f}\#]
"SymbolicLink"="\\\\?\\USB#Vid_04a9&Pid_3074#4&2e05fc02&0&2#{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#USB#Vid_04a9&Pid_3074#4&36c2944&0&2#{6bdd1fc6-810f-11d0-bec7-08002be2092f}]
"DeviceInstance"="USB\\Vid_04a9&Pid_3074\\4&36c2944&0&2"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{6bdd1fc6-810f-11d0-bec7-08002be2092f}\##?#USB#Vid_04a9&Pid_3074#4&36c2944&0&2#{6bdd1fc6-810f-11d0-bec7-08002be2092f}\#]
"SymbolicLink"="\\\\?\\USB#Vid_04a9&Pid_3074#4&36c2944&0&2#{6bdd1fc6-810f-11d0-bec7-08002be2092f}"

Windows 7 64-bit driver for Canon Digital Rebel XT

How do I interface my Canon Digital Rebel XT with a computer running Windows 7 64-bit?

You are correct. Canon does not provide a driver for Windows 7 64-bit. You have to change the communication mode in your camera and then use Windows Photo Gallery or other software to transfer the photos. Here is the response that I received from Canon tech support (it works):
"To connect your camera to a Windows Vista or Windows 7 computer, you'll need to change the communication mode.
To set your camera up for this, please do the following:
With the camera disconnected from the computer, turn the camera on. Press the "Menu" button. Now select the [Wrench, Hammer, 2] tab. Scroll down to "Communication" and press the "Set" button.
Select the [Print/PTP] and press "Set". This process is more completely described (and illustrated too!) on page 121 of your Digital Rebel XT Instruction Manual.
Now connect your camera to your computer and turn the camera on. Your computer should now recognize and have access to your Digital Rebel XT.
Unfortunately, Canon software cannot communicate with the Rebel XT when operating in this mode.
You may download your pictures using Windows Photo Gallery, or you may use a card reader to download images. If you haven't already done so, you may retrieve and install this program from Microsoft's download.live.com."

Camera disconnected at Runtime

Similar Messages

Maybe you are looking for