Hi,

I have installed the latest version of krinnicam on my XP Pro SP3 (German)
system. Unfortunately, the program crashes immediately on startup with the
windows error message "...has detected a problem and will be closed". I have
tried all three versions (usb, serial, dual), and it is the same with every
version.
It happens regardless of wether a camera is connected to the PC or not.

Thanks,

Stefan

I just got digital comcepts 51-in-1 card reader/writer for $19.95+tax
at wal-mart.
Works like a dream :)


--- In krinnicam@yahoogroups.com, "Gareth Hardy" <gareth@...> wrote:
>
> Any that will read compactflash cards.
>
> > Hi all,
> >
> > What's a good but cheap card reader for coolpix 885?
> >
> > Sorry for posting off topic
>

Any that will read compactflash cards.

> Hi all,
>
> What's a good but cheap card reader for coolpix 885?
>
> Sorry for posting off topic

Thanks for the info, I'll check into it :)

--- In krinnicam@yahoogroups.com, Jeff Gutterman <jsgy@...> wrote:
>
> I have a Ratoc Systems International   CF03.  Never had a bit of
trouble after at least 7 years.
> Jeff  
>
> --- On Wed, 2/25/09, aaron_rdmn <aaron_rdmn@...> wrote:
>
> Hi all,
>
> What's a good but cheap card reader for coolpix 885?
>
> Sorry for posting off topic
>

Hi all,

What's a good but cheap card reader for coolpix 885?

Sorry for posting off topic

Hi Jim,

That seems good news to me. We may have it working, I'll try to get
some time for it. To have a more accurate data to work with, you can
try the following:

* create a empty text file and copy/paste the following (substitute
"X:" with the camera drive) :
Dim cp
Set cp = CreateObject("kcamserver.Camera")
cp.ConnectUSB "Coolpix 8800", "X:"
cp.Log(cp.Resolution)
cp.Log(cp.FocalLength)
cp.FocalLength = 63.0
cp.Log(cp.FocalLength)
cp.Shoot
cp.Disconnect
Set cp = Nothing

* name the file something like test.vbs
* set the camera to 'High 2816 x 2112'
* plug the camera to the computer
* when the camera shows as a drive, double-click the file test.vbs:
this will try to connect to the camera, get some information (current
resolution mode and focal length), try to zoom in, then try to shoot.
* look for a file named "log.txt" that should be generated in the same
folder as test.vbs. Please post here the contents of this file.
* check if the camera has changed the focal length and if it actually
shooted.

If the camera shooted, please repeat again but setting a different
resolution, like 'Normal 2816 x 2112', and post also the new log.txt
(the file is recreated each time you run the test.vbs).

With all the information maybe I can add support to krinnicam for this
camera model.

Good luck!


--- In krinnicam@yahoogroups.com, "Jim Davis" <jd_rover4x4@...> wrote:
>
> --- In krinnicam@yahoogroups.com, "aristarco_cjb_net" <aristarco@>
> wrote:
> >
> > Sorry for the long delay.
> >
> > I've been a bit "out" of lastest Nikon models, but I think that these
> > new cameras (S-series, P-series, etc.) are unlikely to work with
> > krinnicam. They seem to be a whole new implementation and won't
> > "speak" the same "language" that the old coolpixes (885, 995, 2500,
> > 3500, 4300, 4500, 5000, 5400, 8400, 8700 and 8800, all discontinued).
> > I haven't got any clue if these are remotelly controllable.
> >
> > Regards,
> > Aristarco
> >
> > --- In krinnicam@yahoogroups.com, "Jin Wu" <jvwu99@> wrote:
> > >
> > > Just purchased a Coolpix S4 (6MP 10x zoom) and tried version 1.06
> > > Krinnicam on both  Win2000 Pro and XP.  The software could not
> > > reconized the camera.  Removalbe drive showed up all right.  We
have 2
> > > CP995's and hope that the software work with this new model of
camera.
> > >  Thanks!   -Jin
> > >
> >
> Hi all. It's been a while since I visited the group (with my new at
> the time CP995!), and since then I see you've come out with  v2..
> GREAT stuff!
>
> I've recently purchased a CP5000 as well as an S4 and I wanted to let
> you know that the S4 DOES connect with v2.0.0.2, and I can get the LCD
> display to toggle on/off. I will also say that I initially connected
> using the std Nikon USB cable that came with the S4, the S4 was set to
> USB "Mass Storage" mode, and Krinnicam was connected as a CP8800. When
> connecting, Krinnicam gave an error that the current focal length
> (6.3) was out of range. When I continued I got your (elegant, btw)
> error handler message but pressed continue rather than quit.
>
> After the error, I proceeded only to test the LCD display, and found
> it worked. I'm afraid to test other functions until I hear from you,
> but I would love to help get this camera working if you have the
> desire. I'll await a reply, and here is the complete error message
detail:
> -----------------------------------------------------------
> See the end of this message for details on invoking
> just-in-time (JIT) debugging instead of this dialog box.
>
> ************** Exception Text **************
> System.ArgumentOutOfRangeException: Value of '6.3' is not valid for
> 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
> Parameter name: Value
>    at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
>    at
>
WindowsApplication1.MainForm.ConnectBackgroundWorker_RunWorkerCompleted(Object
> sender, RunWorkerCompletedEventArgs e)
>    at
>
System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEv\
entArgs
> e)
>    at
>
System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
>
>
> ************** Loaded Assemblies **************
> mscorlib
>     Assembly Version: 2.0.0.0
>     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
>     CodeBase:
> file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
> ----------------------------------------
> krinnicam_usb
>     Assembly Version: 2.0.0.2
>     Win32 Version: 2.0.0.2
>     CodeBase:
> file:///D:/Program%20Files/Photography/krinnicam/krinnicam_usb.exe
> ----------------------------------------
> Microsoft.VisualBasic
>     Assembly Version: 8.0.0.0
>     Win32 Version: 8.0.50727.42 (RTM.050727-4200)
>     CodeBase:
>
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d5\
0a3a/Microsoft.VisualBasic.dll
> ----------------------------------------
> System
>     Assembly Version: 2.0.0.0
>     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
>     CodeBase:
>
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
> ----------------------------------------
> System.Windows.Forms
>     Assembly Version: 2.0.0.0
>     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
>     CodeBase:
>
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e\
089/System.Windows.Forms.dll
> ----------------------------------------
> System.Drawing
>     Assembly Version: 2.0.0.0
>     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
>     CodeBase:
>
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/Sy\
stem.Drawing.dll
> ----------------------------------------
> System.Runtime.Remoting
>     Assembly Version: 2.0.0.0
>     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
>     CodeBase:
>
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c5619\
34e089/System.Runtime.Remoting.dll
> ----------------------------------------
> Interop.KCAMSERVERLib
>     Assembly Version: 2.0.0.0
>     Win32 Version: 2.0.0.0
>     CodeBase:
>
file:///D:/Program%20Files/Photography/krinnicam/Interop.KCAMSERVERLib.DLL
> ----------------------------------------
>
> ************** JIT Debugging **************
> To enable just-in-time (JIT) debugging, the .config file for this
> application or computer (machine.config) must have the
> jitDebugging value set in the system.windows.forms section.
> The application must also be compiled with debugging
> enabled.
>
> For example:
>
> <configuration>
>     <system.windows.forms jitDebugging="true" />
> </configuration>
>
> When JIT debugging is enabled, any unhandled exception
> will be sent to the JIT debugger registered on the computer
> rather than be handled by this dialog box.
>

--- In krinnicam@yahoogroups.com, "aristarco_cjb_net" <aristarco@...>
wrote:
>
> Sorry for the long delay.
>
> I've been a bit "out" of lastest Nikon models, but I think that these
> new cameras (S-series, P-series, etc.) are unlikely to work with
> krinnicam. They seem to be a whole new implementation and won't
> "speak" the same "language" that the old coolpixes (885, 995, 2500,
> 3500, 4300, 4500, 5000, 5400, 8400, 8700 and 8800, all discontinued).
> I haven't got any clue if these are remotelly controllable.
>
> Regards,
> Aristarco
>
> --- In krinnicam@yahoogroups.com, "Jin Wu" <jvwu99@> wrote:
> >
> > Just purchased a Coolpix S4 (6MP 10x zoom) and tried version 1.06
> > Krinnicam on both  Win2000 Pro and XP.  The software could not
> > reconized the camera.  Removalbe drive showed up all right.  We have 2
> > CP995's and hope that the software work with this new model of camera.
> >  Thanks!   -Jin
> >
>
Hi all. It's been a while since I visited the group (with my new at
the time CP995!), and since then I see you've come out with  v2..
GREAT stuff!

I've recently purchased a CP5000 as well as an S4 and I wanted to let
you know that the S4 DOES connect with v2.0.0.2, and I can get the LCD
display to toggle on/off. I will also say that I initially connected
using the std Nikon USB cable that came with the S4, the S4 was set to
USB "Mass Storage" mode, and Krinnicam was connected as a CP8800. When
connecting, Krinnicam gave an error that the current focal length
(6.3) was out of range. When I continued I got your (elegant, btw)
error handler message but pressed continue rather than quit.

After the error, I proceeded only to test the LCD display, and found
it worked. I'm afraid to test other functions until I hear from you,
but I would love to help get this camera working if you have the
desire. I'll await a reply, and here is the complete error message detail:
-----------------------------------------------------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '6.3' is not valid for
'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
    at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
    at
WindowsApplication1.MainForm.ConnectBackgroundWorker_RunWorkerCompleted(Object
sender, RunWorkerCompletedEventArgs e)
    at
System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEv\
entArgs
e)
    at
System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)


************** Loaded Assemblies **************
mscorlib
     Assembly Version: 2.0.0.0
     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
     CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
krinnicam_usb
     Assembly Version: 2.0.0.2
     Win32 Version: 2.0.0.2
     CodeBase:
file:///D:/Program%20Files/Photography/krinnicam/krinnicam_usb.exe
----------------------------------------
Microsoft.VisualBasic
     Assembly Version: 8.0.0.0
     Win32 Version: 8.0.50727.42 (RTM.050727-4200)
     CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d5\
0a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
     Assembly Version: 2.0.0.0
     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
     CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
     Assembly Version: 2.0.0.0
     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
     CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e\
089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
     Assembly Version: 2.0.0.0
     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
     CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/Sy\
stem.Drawing.dll
----------------------------------------
System.Runtime.Remoting
     Assembly Version: 2.0.0.0
     Win32 Version: 2.0.50727.832 (QFE.050727-8300)
     CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c5619\
34e089/System.Runtime.Remoting.dll
----------------------------------------
Interop.KCAMSERVERLib
     Assembly Version: 2.0.0.0
     Win32 Version: 2.0.0.0
     CodeBase:
file:///D:/Program%20Files/Photography/krinnicam/Interop.KCAMSERVERLib.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
     <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Hi,

that seems highly improbable to me. Those newer coolpixes probably
don't share anything with older ones except for the "coolpix"
denomination. There's no other choice but just to try, but I cannot
guarantee anything nor be responsible if these cameras get damaged --
sorry.

There's no report on krinnicam working/not working with coolpix models
after coopix 8800.

--- In krinnicam@yahoogroups.com, "der.sohn" <der.sohn@...> wrote:
>
> Is it possible to control new coolpix models with krinnicam?
> I want to control models Coolpix S700 and Coolpix P5100.
>

Is it possible to control new coolpix models with krinnicam?
I want to control models Coolpix S700 and Coolpix P5100.

It seems that there was a problem with aristarco.com.es hosting. It
should be solved now. Sorry for the inconvenience.

--- In krinnicam@yahoogroups.com, "therealbrewer" <therealbrewer@...>
wrote:
>
> just wondering where I can find your dual-cable instructions...
>
> your web-page seems to have disappeared
>

just wondering where I can find your dual-cable instructions...

your web-page seems to have disappeared

----- Original Message -----

From: Mickey

To: krinnicam@yahoogroups.com

Sent: Friday, March 09, 2007 4:56 AM

Subject: [krinnicam] *.7z

How do I open .7z files?

thx



------------------------ Yahoo! Groups Sponsor --------------------~-->
Something is new at Yahoo! Groups.  Check out the enhanced email design.
http://us.click.yahoo.com/kOt0.A/gOaOAA/yQLSAA/ucIolB/TM
--------------------------------------------------------------------~->

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/krinnicam/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/krinnicam/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:krinnicam-digest@yahoogroups.com
    mailto:krinnicam-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
    krinnicam-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

With the 7-zip file archiver (open source), http://www.7-zip.org/

Regards

--- In krinnicam@yahoogroups.com, "Mickey" <mickey_ym@...> wrote:
>
> How do I open .7z files?
>
> thx
>

How do I open .7z files?

thx

• Bugs resolved:
  #1676778 Custom download folder/file patterns won't work
  #1676691 LCD goes black after downloading a picture (USB)
• Feature requests:
  #1676773 Specify filename without any pattern
• krinnicam core API new property: IsLCDOn

Hi, and thanks for the input.
I use the camera with the AC adapter, so I leave the LCD on all the
time. That's when I noticed the behaviour.
Let me know if you get around to figuring it out. All in all though,
this is one fantastic program you've written.
Well done.

Bob

--- In krinnicam@yahoogroups.com, "aristarco_cjb_net" <aristarco@...>
wrote:
>
> Ok, I've confirmed this problem. I really didn't experience it before
> because I usually keep the LCD off while shooting to save battery
> (this is recommended) -- I just turn it on to frame the picture.
>
> It seems to be a side effect of the "erase command" that krinnicam
> sends to the camera after downloading a picture (to free memory on the
> flash card). This is a camera firmware issue, so I cannot really fix
> it, just code a workaround in krinnicam (i.e., force the LCD to be
> on). Unfortunately, this solution implies an increase in the time
> required to shoot a picture, so intervals will have to be larger
> consequently (so here is another reason to keep LCD off while
shooting).
>
> I'll report back when I'm done fixing this problem (it will take a
> while as I'm a bit busy nowadays).
>
> Thank you for the bug report.
> Regards,
> Aristarco
>
> --- In krinnicam@yahoogroups.com, "aristarco_cjb_net" <aristarco@>
> wrote:
> >
> > Ok, I'll check this as soon as I can spare some time. Thank you for
> > the detailed information.
> > Regards,
> > Aristarco
> >
> > --- In krinnicam@yahoogroups.com, "bobcadlo" <bobcadlo@> wrote:
> > >
> > > Just as a follow-up, I should have been more specific. The LCD only
> > > turns off after the first shot if I am having the program
download the
> > > file after each shot.
> > > Here is the log file for connecting, turning on the LCD, taking one
> > > exposure with download. The LCD turned itself off after the
download.
> > >
> > >
> > > Open log: 2007-03-04 20:32:19.976
> > > 20:32:19.976 starting kcamserver v2.01...
> > > 20:32:19.976 IsWin98(GetVersionEx): No [Platform 2, v5.01.2600
> > > (Service Pack 2)]
> > > 20:32:20.194 get_DownloadBasePath: "C:\Documents and Settings\bob\My
> > > Documents"
> > > 20:32:27.835 ConnectUSB: connecting to Coolpix 8400 in Y:
> > > 20:32:27.835 OpenUSB IOCTL: Y
> > > 20:32:27.835 Create IOCTL_DSC USB\Y:
> > > 20:32:27.835 ConnectUSB: NIKON    NIKON DSC E8400  1.00
> > > 20:32:27.851 ConnectUSB: camera firmware version v789-80
> > > 20:32:27.882 ConnectUSB: autoshutdown timer set to 30'
> > > 20:32:27.944 get_Battery: 100 %
> > > 20:32:27.960 get_Resolution: 640x480 Basic
> > > 20:32:27.991 get_WhiteBalance: Auto
> > > 20:32:28.007 get_Focus: Macro
> > > 20:32:28.038 get_Flash: Off
> > > 20:32:28.054 get_EVCompensation: -1.7
> > > 20:32:28.085 get_Metering: Spot
> > > 20:32:28.116 get_FocalLength: 6.1 mm
> > > 20:32:28.116 get_DownloadBehaviour: Off
> > > 20:32:28.116 get_DownloadFilePattern: KCAM%s
> > > 20:32:28.116 get_DownloadFolderPattern:
> > > 20:32:35.554 TurnLCDOn: done
> > > 20:32:38.991 put_DownloadBehaviour: After each shot
> > > 20:32:48.788 put_DownloadBasePath: "C:\Documents and Settings\bob\My
> > > Documents"
> > > 20:32:48.819 ShootSequence: 1, 0.0, 0.0
> > > 20:32:57.429 ShootSequence: shot #1 ok
> > > 20:33:03.944 DownloadAfterEach: downloaded picture #1 ("C:\Documents
> > > and Settings\bob\My Documents\KCAM0001.JPG")...
> > > 20:33:03.944 ShootSequence: 1 shots, 1 pictures downloaded
> > > 20:33:07.304 Destroy IOCTL_DSC USB\Y:
> > > 20:33:07.304 Disconnect: camera disconnected
> > > Close log: 2007-03-04 20:33:11.538
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --- In krinnicam@yahoogroups.com, "bobcadlo" <bobcadlo@> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm using the latest version of the program with a Coolpix 8400.
> > > > Everything seems to work fine except that when I turn on the LCD
> > > > display with the program, it turns off the display after the first
> > > > exposure, and it just stays off. The button still reads "Turn LCD
> > off".
> > > >
> > > > Any ideas?
> > > >
> > > > Thanks,
> > > > Bob
> > > >
> > >
> >
>

Ok, I've confirmed this problem. I really didn't experience it before
because I usually keep the LCD off while shooting to save battery
(this is recommended) -- I just turn it on to frame the picture.

It seems to be a side effect of the "erase command" that krinnicam
sends to the camera after downloading a picture (to free memory on the
flash card). This is a camera firmware issue, so I cannot really fix
it, just code a workaround in krinnicam (i.e., force the LCD to be
on). Unfortunately, this solution implies an increase in the time
required to shoot a picture, so intervals will have to be larger
consequently (so here is another reason to keep LCD off while shooting).

I'll report back when I'm done fixing this problem (it will take a
while as I'm a bit busy nowadays).

Thank you for the bug report.
Regards,
Aristarco

--- In krinnicam@yahoogroups.com, "aristarco_cjb_net" <aristarco@...>
wrote:
>
> Ok, I'll check this as soon as I can spare some time. Thank you for
> the detailed information.
> Regards,
> Aristarco
>
> --- In krinnicam@yahoogroups.com, "bobcadlo" <bobcadlo@> wrote:
> >
> > Just as a follow-up, I should have been more specific. The LCD only
> > turns off after the first shot if I am having the program download the
> > file after each shot.
> > Here is the log file for connecting, turning on the LCD, taking one
> > exposure with download. The LCD turned itself off after the download.
> >
> >
> > Open log: 2007-03-04 20:32:19.976
> > 20:32:19.976 starting kcamserver v2.01...
> > 20:32:19.976 IsWin98(GetVersionEx): No [Platform 2, v5.01.2600
> > (Service Pack 2)]
> > 20:32:20.194 get_DownloadBasePath: "C:\Documents and Settings\bob\My
> > Documents"
> > 20:32:27.835 ConnectUSB: connecting to Coolpix 8400 in Y:
> > 20:32:27.835 OpenUSB IOCTL: Y
> > 20:32:27.835 Create IOCTL_DSC USB\Y:
> > 20:32:27.835 ConnectUSB: NIKON    NIKON DSC E8400  1.00
> > 20:32:27.851 ConnectUSB: camera firmware version v789-80
> > 20:32:27.882 ConnectUSB: autoshutdown timer set to 30'
> > 20:32:27.944 get_Battery: 100 %
> > 20:32:27.960 get_Resolution: 640x480 Basic
> > 20:32:27.991 get_WhiteBalance: Auto
> > 20:32:28.007 get_Focus: Macro
> > 20:32:28.038 get_Flash: Off
> > 20:32:28.054 get_EVCompensation: -1.7
> > 20:32:28.085 get_Metering: Spot
> > 20:32:28.116 get_FocalLength: 6.1 mm
> > 20:32:28.116 get_DownloadBehaviour: Off
> > 20:32:28.116 get_DownloadFilePattern: KCAM%s
> > 20:32:28.116 get_DownloadFolderPattern:
> > 20:32:35.554 TurnLCDOn: done
> > 20:32:38.991 put_DownloadBehaviour: After each shot
> > 20:32:48.788 put_DownloadBasePath: "C:\Documents and Settings\bob\My
> > Documents"
> > 20:32:48.819 ShootSequence: 1, 0.0, 0.0
> > 20:32:57.429 ShootSequence: shot #1 ok
> > 20:33:03.944 DownloadAfterEach: downloaded picture #1 ("C:\Documents
> > and Settings\bob\My Documents\KCAM0001.JPG")...
> > 20:33:03.944 ShootSequence: 1 shots, 1 pictures downloaded
> > 20:33:07.304 Destroy IOCTL_DSC USB\Y:
> > 20:33:07.304 Disconnect: camera disconnected
> > Close log: 2007-03-04 20:33:11.538
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --- In krinnicam@yahoogroups.com, "bobcadlo" <bobcadlo@> wrote:
> > >
> > > Hi,
> > >
> > > I'm using the latest version of the program with a Coolpix 8400.
> > > Everything seems to work fine except that when I turn on the LCD
> > > display with the program, it turns off the display after the first
> > > exposure, and it just stays off. The button still reads "Turn LCD
> off".
> > >
> > > Any ideas?
> > >
> > > Thanks,
> > > Bob
> > >
> >
>

Ok, I'll check this as soon as I can spare some time. Thank you for
the detailed information.
Regards,
Aristarco

--- In krinnicam@yahoogroups.com, "bobcadlo" <bobcadlo@...> wrote:
>
> Just as a follow-up, I should have been more specific. The LCD only
> turns off after the first shot if I am having the program download the
> file after each shot.
> Here is the log file for connecting, turning on the LCD, taking one
> exposure with download. The LCD turned itself off after the download.
>
>
> Open log: 2007-03-04 20:32:19.976
> 20:32:19.976 starting kcamserver v2.01...
> 20:32:19.976 IsWin98(GetVersionEx): No [Platform 2, v5.01.2600
> (Service Pack 2)]
> 20:32:20.194 get_DownloadBasePath: "C:\Documents and Settings\bob\My
> Documents"
> 20:32:27.835 ConnectUSB: connecting to Coolpix 8400 in Y:
> 20:32:27.835 OpenUSB IOCTL: Y
> 20:32:27.835 Create IOCTL_DSC USB\Y:
> 20:32:27.835 ConnectUSB: NIKON    NIKON DSC E8400  1.00
> 20:32:27.851 ConnectUSB: camera firmware version v789-80
> 20:32:27.882 ConnectUSB: autoshutdown timer set to 30'
> 20:32:27.944 get_Battery: 100 %
> 20:32:27.960 get_Resolution: 640x480 Basic
> 20:32:27.991 get_WhiteBalance: Auto
> 20:32:28.007 get_Focus: Macro
> 20:32:28.038 get_Flash: Off
> 20:32:28.054 get_EVCompensation: -1.7
> 20:32:28.085 get_Metering: Spot
> 20:32:28.116 get_FocalLength: 6.1 mm
> 20:32:28.116 get_DownloadBehaviour: Off
> 20:32:28.116 get_DownloadFilePattern: KCAM%s
> 20:32:28.116 get_DownloadFolderPattern:
> 20:32:35.554 TurnLCDOn: done
> 20:32:38.991 put_DownloadBehaviour: After each shot
> 20:32:48.788 put_DownloadBasePath: "C:\Documents and Settings\bob\My
> Documents"
> 20:32:48.819 ShootSequence: 1, 0.0, 0.0
> 20:32:57.429 ShootSequence: shot #1 ok
> 20:33:03.944 DownloadAfterEach: downloaded picture #1 ("C:\Documents
> and Settings\bob\My Documents\KCAM0001.JPG")...
> 20:33:03.944 ShootSequence: 1 shots, 1 pictures downloaded
> 20:33:07.304 Destroy IOCTL_DSC USB\Y:
> 20:33:07.304 Disconnect: camera disconnected
> Close log: 2007-03-04 20:33:11.538
>
>
>
>
>
>
>
>
>
>
> --- In krinnicam@yahoogroups.com, "bobcadlo" <bobcadlo@> wrote:
> >
> > Hi,
> >
> > I'm using the latest version of the program with a Coolpix 8400.
> > Everything seems to work fine except that when I turn on the LCD
> > display with the program, it turns off the display after the first
> > exposure, and it just stays off. The button still reads "Turn LCD
off".
> >
> > Any ideas?
> >
> > Thanks,
> > Bob
> >
>

Just as a follow-up, I should have been more specific. The LCD only
turns off after the first shot if I am having the program download the
file after each shot.
Here is the log file for connecting, turning on the LCD, taking one
exposure with download. The LCD turned itself off after the download.


Open log: 2007-03-04 20:32:19.976
20:32:19.976 starting kcamserver v2.01...
20:32:19.976 IsWin98(GetVersionEx): No [Platform 2, v5.01.2600
(Service Pack 2)]
20:32:20.194 get_DownloadBasePath: "C:\Documents and Settings\bob\My
Documents"
20:32:27.835 ConnectUSB: connecting to Coolpix 8400 in Y:
20:32:27.835 OpenUSB IOCTL: Y
20:32:27.835 Create IOCTL_DSC USB\Y:
20:32:27.835 ConnectUSB: NIKON    NIKON DSC E8400  1.00
20:32:27.851 ConnectUSB: camera firmware version v789-80
20:32:27.882 ConnectUSB: autoshutdown timer set to 30'
20:32:27.944 get_Battery: 100 %
20:32:27.960 get_Resolution: 640x480 Basic
20:32:27.991 get_WhiteBalance: Auto
20:32:28.007 get_Focus: Macro
20:32:28.038 get_Flash: Off
20:32:28.054 get_EVCompensation: -1.7
20:32:28.085 get_Metering: Spot
20:32:28.116 get_FocalLength: 6.1 mm
20:32:28.116 get_DownloadBehaviour: Off
20:32:28.116 get_DownloadFilePattern: KCAM%s
20:32:28.116 get_DownloadFolderPattern:
20:32:35.554 TurnLCDOn: done
20:32:38.991 put_DownloadBehaviour: After each shot
20:32:48.788 put_DownloadBasePath: "C:\Documents and Settings\bob\My
Documents"
20:32:48.819 ShootSequence: 1, 0.0, 0.0
20:32:57.429 ShootSequence: shot #1 ok
20:33:03.944 DownloadAfterEach: downloaded picture #1 ("C:\Documents
and Settings\bob\My Documents\KCAM0001.JPG")...
20:33:03.944 ShootSequence: 1 shots, 1 pictures downloaded
20:33:07.304 Destroy IOCTL_DSC USB\Y:
20:33:07.304 Disconnect: camera disconnected
Close log: 2007-03-04 20:33:11.538










--- In krinnicam@yahoogroups.com, "bobcadlo" <bobcadlo@...> wrote:
>
> Hi,
>
> I'm using the latest version of the program with a Coolpix 8400.
> Everything seems to work fine except that when I turn on the LCD
> display with the program, it turns off the display after the first
> exposure, and it just stays off. The button still reads "Turn LCD off".
>
> Any ideas?
>
> Thanks,
> Bob
>

Hi,

I'm using the latest version of the program with a Coolpix 8400.
Everything seems to work fine except that when I turn on the LCD
display with the program, it turns off the display after the first
exposure, and it just stays off. The button still reads "Turn LCD off".

Any ideas?

Thanks,
Bob

Hi Marco,

first of all I'm terribly sorry for this very very long delay. I've
been very busy and didn't have any spare time for almost anything else
than having some rest. I note your suggestions down and I hope the
next release will solve the problems you describe. I'm quite confident
that it won't be very hard, but the truth is that it's so long since
the last time I worked on the code that I need to sit down and
evaluate how difficult it would be.

Best Regards,
Aristarco

--- In krinnicam@yahoogroups.com, "marco_brugnara"
<marco_brugnara@...> wrote:
>
> Dear Aristarco,
> I tried to contact you also in email, but I'm not sure about the
address so I'll post also here
> my "request".
> Thanks to your new effort with the version 2 of your software, I
decided to write a labview
> program, which using the camera server, can control the camera and
then directly analyze
> the picture. A great step ahead, so thank you alot!
>
> Just I saw that in the new library there is a small bug, which is
quite annoying, that's the
> reason of this email. It would be awesome if you can correct it in
the next review!
> The problem comes with the file name: differently from the past
version the new version
> doesn't allow to let the original name (dscXXXXX) but it is
compulsory to give a name when
> the picture is automatically downloaded.
> No problem, just it could be useful to have also this possibility.
> But the main trouble is that it is not possible to give a generic name!
> The "DownloadFilePattern" accept only names having "%s" or"%d" or
"%t" at their end. For
> instance, if I try to set as name "marco", the picture is downloaded
as "marco0001" and
> this is a big trouble for me. Not only: if in the same session I
rename this picture as
> "picture", so it doesn't exist a "marco0001" file in the folder, and
I shot another pic, even
> with the DownloadFilePattern setted with "marco", the picture is
downloaded as
> marco0002.
> I saw that even using your code with krinnicam2, the possibility to
give a single name
> without numbers doesn't work.
> That's all!
>
> Do you think it is possible to you to fix this bug?
> Thank you alot and best regards,
> Marco
>

Dear Aristarco,
I tried to contact you also in email, but I'm not sure about the address so I'll
post also here
my "request".
Thanks to your new effort with the version 2 of your software, I decided to
write a labview
program, which using the camera server, can control the camera and then directly
analyze
the picture. A great step ahead, so thank you alot!

Just I saw that in the new library there is a small bug, which is quite
annoying, that's the
reason of this email. It would be awesome if you can correct it in the next
review!
The problem comes with the file name: differently from the past version the new
version
doesn't allow to let the original name (dscXXXXX) but it is compulsory to give a
name when
the picture is automatically downloaded.
No problem, just it could be useful to have also this possibility.
But the main trouble is that it is not possible to give a generic name!
The "DownloadFilePattern" accept only names having "%s" or"%d" or "%t" at their
end. For
instance, if I try to set as name "marco", the picture is downloaded as
"marco0001" and
this is a big trouble for me. Not only: if in the same session I rename this
picture as
"picture", so it doesn't exist a "marco0001" file in the folder, and I shot
another pic, even
with the DownloadFilePattern setted with "marco", the picture is downloaded as
marco0002.
I saw that even using your code with krinnicam2, the possibility to give a
single name
without numbers doesn't work.
That's all!

Do you think it is possible to you to fix this bug?
Thank you alot and best regards,
Marco

Hi,
Thanks for your reply!  It's now obvious why the focal length setting
wouldn't work :)

And the URL you pointed me towards was exactly the one I had in mind.
  Thanks!
Matt

--- In krinnicam@yahoogroups.com, "mconsidine_1999" <matt@...> wrote:
>
> Hi,
> Nice bit of software.  Two questions :
> - I checked the archives but did not readily see an answer to the
> question of whether or not I can set the focal length via a USB cable.
>  More specifically, when I hook a CP 4300 (firmware 1.5) up to the
> computer via the USB cable, I *cannot* set the focal length.  Am I
> missing something?

Hi, Matt:

Unfortunately the focal length can only be set on CP885, CP995 and
CP4500. The rest of coolpixes (which are newer models) simply ignore
the setting, although it seems that the focal length is correctly read
by krinnicam. This is a consequence of not knowing the internals of
the Nikon cameras, all the information we have about them has been got
by trial and error.

Another examples are the aperture and shutter speed settings: they can
be remotely controlled in an old CP990 but not in the post-995 models.
A pity.

> - I thought I had recalled seeing where someone had figured out how to
> modify the firmware to save pictures in the native RAW/NEF format as
> well.  Does anyone have that URL handy?

For a CP4300 you don't need to update the firmware, just run the
"coolpix raw enabler" which you can download from
http://e2500.narod.ru/cpixraw_v0.03.zip
This enables the RAW mode on the camera, but the RAW files are not in
standart format. To get NEF or DNG files, you can try this converter:
http://e2500.narod.ru/raw2nef_e.htm

I didn't check these out myself; if you try them, I would like to hear
about your experience.

Regards,
Aristarco

Hi,
Nice bit of software.  Two questions :
- I checked the archives but did not readily see an answer to the
question of whether or not I can set the focal length via a USB cable.
  More specifically, when I hook a CP 4300 (firmware 1.5) up to the
computer via the USB cable, I *cannot* set the focal length.  Am I
missing something?
- I thought I had recalled seeing where someone had figured out how to
modify the firmware to save pictures in the native RAW/NEF format as
well.  Does anyone have that URL handy?

Thanks in advance and sorry if any of these answers are obvious.  I
did try to search first!

Regards,
Matt

Ok, I'll give it a chance :o))

THANKS

Cla.

--- In krinnicam@yahoogroups.com, "aristarco_cjb_net" <aristarco@...>
wrote:
>
> I can't figure what's wrong. I'm releasing v2.01 solving those
> reported issues with the download folder, while I keep on your
> problem. Anyway, have a look at this new release to check if it's
> solved collaterally (by chance, I mean :) ... but I don't think so,
> actually.)
>
> Thanks for your help.
> Regards
> Aristarco
>
> --- In krinnicam@yahoogroups.com, "Claudio" <jas_cla_66@> wrote:
> >
> > Ola` :o)
> >
> > This standalone OpenFolder Dialog works flawlessly :o))))).
> >
> > I try do dig more into the problem.
> >
> > Ciao
> >
> > Cla.
> >
> > --- In krinnicam@yahoogroups.com, "aristarco_cjb_net"
<aristarco@>
> > wrote:
> > >
> > > Claudio,
> > >
> > > I cannot reproduce this problem. I've uploaded a test (look for
> > > "testFolderDlg" in Files section) to determine if there is some
> > > problem with the dialog itself. Please check it out if you have
a
> > minute.
> > >
> > > Thanks
> > > Aristarco
> > >
> > > --- In krinnicam@yahoogroups.com, "Claudio" <jas_cla_66@> wrote:
> > > >
> > > >
> > > > The "G:" is my 2nd internal HDU and yes, I can browse and
> > (luckily)
> > > > use all the data I've on it :o)))
> > > >
> > > > Isn't a bis issue, however it happen.
> > > >
> > > > Bye
> > > >
> > > > Cla.
> > > >
> > > > --- In krinnicam@yahoogroups.com, "aristarco_cjb_net"
> > <aristarco@>
> > > > wrote:
> > > > >
> > > > > There is a bug in the krinnicam interface so that no matter
> > what you
> > > > > set as download base path, it isn't transferred to the core
> > module.
> > > > So
> > > > > krinnicam ends up writing every picture at the default
folder.
> > This
> > > > is
> > > > > what Leon Gent described. This bug has been solved for the
next
> > > > release.
> > > > >
> > > > > In your case, there is something weird that brings up that
> > > > exception.
> > > > > As krinnicam (core) can't get any "correct" value as
download
> > path,
> > > > it
> > > > > takes the default folder.
> > > > > What is 'G:\'? Can you browse files in G:\? The "..."
button
> > just
> > > > > displays the system folder dialog, nothing fancy in that...
> > > > >
> > > > > Thank you!
> > > > >
> > > > >
> > > > >
> > > > > --- In krinnicam@yahoogroups.com, "Claudio" <jas_cla_66@>
wrote:
> > > > > >
> > > > > > Hi Aristarco, this seems to be a correlated problem. I
> > uploaded 2
> > > > > > images in the photos/misc area with 2 screenshots ot the
> > > > situation.
> > > > > > If I depress the browse [...] button I receive an error
(I
> > can't
> > > > > > capture it) with an error of "Impossible to find the disk
in
> > the
> > > > unit
> > > > > > \device\harddisk3\dr13".
> > > > > >
> > > > > > I hope this help.
> > > > > >
> > > > > > Bye
> > > > > >
> > > > > > Cla.
> > > >
> > >
> >
>

I can't figure what's wrong. I'm releasing v2.01 solving those
reported issues with the download folder, while I keep on your
problem. Anyway, have a look at this new release to check if it's
solved collaterally (by chance, I mean :) ... but I don't think so,
actually.)

Thanks for your help.
Regards
Aristarco

--- In krinnicam@yahoogroups.com, "Claudio" <jas_cla_66@...> wrote:
>
> Ola` :o)
>
> This standalone OpenFolder Dialog works flawlessly :o))))).
>
> I try do dig more into the problem.
>
> Ciao
>
> Cla.
>
> --- In krinnicam@yahoogroups.com, "aristarco_cjb_net" <aristarco@>
> wrote:
> >
> > Claudio,
> >
> > I cannot reproduce this problem. I've uploaded a test (look for
> > "testFolderDlg" in Files section) to determine if there is some
> > problem with the dialog itself. Please check it out if you have a
> minute.
> >
> > Thanks
> > Aristarco
> >
> > --- In krinnicam@yahoogroups.com, "Claudio" <jas_cla_66@> wrote:
> > >
> > >
> > > The "G:" is my 2nd internal HDU and yes, I can browse and
> (luckily)
> > > use all the data I've on it :o)))
> > >
> > > Isn't a bis issue, however it happen.
> > >
> > > Bye
> > >
> > > Cla.
> > >
> > > --- In krinnicam@yahoogroups.com, "aristarco_cjb_net"
> <aristarco@>
> > > wrote:
> > > >
> > > > There is a bug in the krinnicam interface so that no matter
> what you
> > > > set as download base path, it isn't transferred to the core
> module.
> > > So
> > > > krinnicam ends up writing every picture at the default folder.
> This
> > > is
> > > > what Leon Gent described. This bug has been solved for the next
> > > release.
> > > >
> > > > In your case, there is something weird that brings up that
> > > exception.
> > > > As krinnicam (core) can't get any "correct" value as download
> path,
> > > it
> > > > takes the default folder.
> > > > What is 'G:\'? Can you browse files in G:\? The "..." button
> just
> > > > displays the system folder dialog, nothing fancy in that...
> > > >
> > > > Thank you!
> > > >
> > > >
> > > >
> > > > --- In krinnicam@yahoogroups.com, "Claudio" <jas_cla_66@> wrote:
> > > > >
> > > > > Hi Aristarco, this seems to be a correlated problem. I
> uploaded 2
> > > > > images in the photos/misc area with 2 screenshots ot the
> > > situation.
> > > > > If I depress the browse [...] button I receive an error (I
> can't
> > > > > capture it) with an error of "Impossible to find the disk in
> the
> > > unit
> > > > > \device\harddisk3\dr13".
> > > > >
> > > > > I hope this help.
> > > > >
> > > > > Bye
> > > > >
> > > > > Cla.
> > >
> >
>