Device not connected – Ensure that the device is switched on or not being used by another program

Grazie wrote on 7/17/2002, 2:26 PM
Anybody got/had this one yet? Course you have!

I did, today. After much, much “Capturing” ON my Dazzle and ON WinME the dreaded “Device not connected…” reared its ugly head. Oooh err!

Hmmmmm…. Let me try Studio7. Yup everything is hunky dory (where does that phrase come from?).

Soooo all the cabling and the Dazzle are working and the capturing is going on to my external Maxtor Firewire – no problemo.

Do a defrag, system restore etc etc. VF still “Device not ….” etc etc.

Just because I want to capture to a new folder on the F: drive I decided to go to the Capture preferences> file management thingy…. Oh er!?! No F: drive folder path. Yes, there is F: sitting there – but, no path or evidence of the 80gb and the £180.00 I’ve just lashed out for it!

Oh no the drive is fried!!!! Woah there Grazie – calm down, calm down - see if there is anything showing on WinExplorer. Phew – all is there. All is right and correct. Sooooo I now set up a new capture folder on F: and the whole system decides to spring back into life. – Yes I understand there has been some “drop” in the path direction/connection. But, and this is the real reason for posting this, why on earth does VF try to insinuate that the capture “Device…” is not connected? Does this mean that the capture folder had lost its way? Or does it mean that the Dazzle or camera is not sending stuff to be captured because it aint behaving itself. Why on earth does not VF say something like “VF can not capture to requested folder. Ensure drive is connected by looking in File Management under Preferences for Capture” – or something of the ilk! It was a bit ambiguous – don’t you think?

Is this a “Bug” I see before me? At least SoFo should have a look at it too.

Anyway, Vfers if you get the “Device not connected…..” do, do have a look-see at the file management for capturing, and confirm or set-up what you would have expected to see.

I do hope this helps someone out there.

Grazie

PS - I am still waiting for the Canon XM2/GL2 to emerge in the UK!!!!!!!

Comments

BillyBoy wrote on 7/17/2002, 3:10 PM
The 'device not connected' message is most probably due to your operating system burping. Common sense should tell you if VF works sometimes then not other times, then there isn't anything likely wrong with the application and you should focus your attention to either the device or the operating system.

I've used personal computers for close to 25 years. I could write a book on all the weird stuff that happens for no apparant reason. Almost all of it is the fault of WINDOWS. Is anyone really that surprised?

Before jumping to extraordinary steps like defraging or reinstalling any application or Winodws itself try simpler things. Like do a full shutdown and a cold reboot. Windows versions prior to XP can exhaust system resources and a simple reboot cures many strange happenings. With external devices Windows may at times get "blinded" and cause stupid messages like 'device not connected'. Almost always any firewire device can be reinitialized by rebooting, waiting for the system to come up, then reinsert the firewire cable. Like magic, you'll solve your problem.

Grazie wrote on 7/17/2002, 4:00 PM
Lovely, lovely, lovely.....

"Common sense should tell you...., then there isn't anything likely wrong with the application and you should focus your attention to either the device or the operating system" - Common sense - I wouldn't say your 25 years of experience is ... common!

"Before jumping to extraordinary steps like defraging or reinstalling any application or Winodws itself" - Extraordinary, woah there!

"With external devices Windows may at times get "blinded" and cause stupid messages like 'device not connected'" - this came from within VF. Oh yeah it didn't happen in Studio7 so maybe it aint WinME telling me this. Are you saying WinME is giving me this message or VF?

"Almost always any firewire device can be reinitialized by rebooting, waiting for the system to come up, then reinsert the firewire cable. Like magic, you'll solve your problem." - Did the reboot thing - twice! Studio7 didn't have a capture problem.

"Before jumping to extraordinary steps like defraging or reinstalling any application or Winodws itself try simpler things. Like do a full shutdown and a cold reboot." - Did this as well - sorry only 15 years of experience here with MSDOS and then Win3 etc etc - granted not "under the bonnet" stuff, but y'know, I'm one of those trusting souls who's trying to make his way in life.

What I find "extraordinary" about your reply is that I may, just may have come up with a possible - in my most humble opinion - a possible "misleading" error message and within, I think, VF. That's all.

"Like magic, you'll solve your problem" - Nah, I won't rise to that one!

BillyBoy thanks for your instructive and thought provoking missive...

However and yes -what do you think about my comment on my suggestion for VF telling me a more plausible identifacation of the problem? I believe, and I am sure you know it too, with your 25 years of experience, that many many programs are improved by Newbies [myself included] BETA-ing and using packages.

Positive criticism is where I'm coming from. Oh yeah and I try to do this with a tad of humour into the process. - That's my experience.... for what it's worth.

I still love my VF. Just to remind myself what an excellent package it is, I go back to and look and hear the angst on the "Dark-Side". You should see one of the latest posts there. It's precious!

BB "May the Force Be With You."

Grazie
BillyBoy wrote on 7/17/2002, 5:08 PM
What I find extraordinary in your comments is you don't have a clue, you admit you're a newbie, you admit you don't know what's wrong yet when someone tries to help you, instead of appreciating the attempt you throw it back in their face. You're frustrated and it shows. There are many things you could try and I would have gladly told you what next to do. Now that you instead decided to cop an attitude you can forgot about getting any further help from me on this topic.

miketree wrote on 7/18/2002, 3:43 AM
Grazie, I've had that problem too. Last weeknd VF would not recognise my Sony DV camcorder. With my admitedly meagre 20 years of computing experience it took me most of the day to get it working again, trying all the things mentioned above and more. It worked with my Videowave software fine.

Would you like to know what actually fixed it? Well so would I !! It just started working. I agree with you. If one piece of software captures fine, but another doesn't, there must be a problem. After all, they use the same firewire/dv drivers.

Perhaps SF could look into this problem.

Apart from that, I'm a really happy bunny. I can honestly say VF is the best value piece of software I've ever bought.

p.s. Using Win98se
Grazie wrote on 7/18/2002, 5:26 AM
Thanks for that Miketree. Yes, SoFo might give it a whizz and check it out.

Yup me too - very happy rabbit!

I can "force" the correction by viewing the Folder management thingy in Capture Preferences - while in capture - to "re-connect" to the path and drive I started with. THEN things work fine.

Regards

Grazie