| Author |
Message |
doubleoghand
Joined: 30 Apr 2005
Posts: 3
|
 Posted:
Thu May 19, 2005 11:23 pm |
  |
Has anyone been able to "modify" the CVS camcorder yet? I have been messing around with one for a couple of weeks and can still only get windows to just see new hardware. |
|
|
  |
|
teslafreak
Joined: 04 May 2005
Posts: 105
|
| Posted:
Thu May 19, 2005 11:32 pm |
|
proabally the next step is to see what chipset is inside
and see if its used in other portable video recorders
and try to get access through similar drivers
but proabally there will be a similar lock and a set of keys
will have to be aquirred (a coustom flash reader)
welcone to camera hacking
teslafreak |
|
|
|
|
brite_eye
Joined: 14 Apr 2005
Posts: 2518
Location: In my dreams higher than a kite as a wingsuit flyer
|
| Posted:
Fri May 20, 2005 12:37 am |
|
|
 |
|
dakotamod
Joined: 15 Apr 2005
Posts: 49
Location: Twilight Zone, brite_begone
|
| Posted:
Fri May 20, 2005 12:41 am |
|
Some details (from codeknowbi):
Fujitsu Millennia 3MM MB91382
256MB flash storage
8 and 16MB RAM chips
2MB chip for firmware |
|
|
|
|
codeknowbi
Joined: 22 Apr 2005
Posts: 10
Location: Phoenix,AZ
|
| Posted:
Sun May 22, 2005 5:17 am |
|
some interesting info from PV2Resurrector info frame
| Quote: |
878248 USB id 4146/4146, configuration 00, interface 00, alternate setting 00
Bulkout = 02 Bulkin = 81
878480 USB id 0EA0/6803, configuration 00, interface 00, alternate setting 00
Bulkout = 02 Bulkin = 81
878248 USB id 0DCA/0027, configuration 00, interface 00, alternate setting 00
Bulkout = 01 Bulkin = 81
877CC8 USB id 04C5/2003, configuration 00, interface 00, alternate setting 00
Bulkout = 01 Bulkin = 82 |
the first 2 are thumb drives
the 3rd is a pv2
the 4th is the cvs camcorder
I'm guessing that the current tools could be altered to poke at the camcorder |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Tue May 24, 2005 10:56 pm |
|
This now appears to be available in the Delaware area. At least a CVS on the border with PA had them (though out of stock by the time I got there...) |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Wed May 25, 2005 4:28 pm |
|
Went to a different CVS in the same area and they had one left, which I now have. I don't see any dates on the packaging but will post more tonight.
Does it make sense to start a new area for camcorder-only threads? |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Wed May 25, 2005 10:36 pm |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Sat May 28, 2005 3:30 pm |
|
| codeknowbi wrote: |
some interesting info from PV2Resurrector info frame
| Quote: |
878248 USB id 4146/4146, configuration 00, interface 00, alternate setting 00
Bulkout = 02 Bulkin = 81
878480 USB id 0EA0/6803, configuration 00, interface 00, alternate setting 00
Bulkout = 02 Bulkin = 81
878248 USB id 0DCA/0027, configuration 00, interface 00, alternate setting 00
Bulkout = 01 Bulkin = 81
877CC8 USB id 04C5/2003, configuration 00, interface 00, alternate setting 00
Bulkout = 01 Bulkin = 82 |
the first 2 are thumb drives
the 3rd is a pv2
the 4th is the cvs camcorder
I'm guessing that the current tools could be altered to poke at the camcorder |
I don't get anything from PV2Resurrector upon plug-in. Also, device manager is only showing me
VID=167b PID=0101
Installing the AIPTek software and changing the relevant drivers only gets me a message saying it can't start the device.
Adding a line for this VID/PID combo in the SMaL INF files and then firing up IRFANVIEW doesn't get me anywhere.
If anyone has any other thoughts on how to probe this, let me know.
(Trivia info : this is a USB 2.0 compatible device and will work without batteries but tethered to a PC) |
|
|
|
|
daBass
Joined: 16 Apr 2005
Posts: 75
Location: the Netherlands
|
| Posted:
Sat May 28, 2005 3:55 pm |
|
Now this is interesting:
| Quote: |
877CC8 USB id 04C5/2003, configuration 00, interface 00, alternate setting 00
Bulkout = 01 Bulkin = 82 |
04C5 default Fujitsu USB vendor ID
Which is an unknown USB vendor ID. My guess is that your cable isn't correct.
Also, if you want to start playing with existing drivers, have a look at the
FinePix drivers.
Is it already known in which states these disposable camcorders are available? |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Sat May 28, 2005 4:57 pm |
|
I suppose it's possible that the connector I soldered to the board is off a bit, but a close look under magnifying lenses shows no obvious problem with the board connections. And the cable I'm using works fine on a CVS Red. So I think my connections are okay.
At one point when I was futzing around with drivers and INF files, I got the following readout from the libusb test program :
====================================
bus-0/.libusb0-0002--0x167b-0x0101 167B/0101
- Manufacturer : Pure Digital Inc.
- Product : Saturn
- Serial Number: PS0000010
wTotalLength: 39
bNumInterfaces: 1
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 80h
MaxPower: 48
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 3
bInterfaceClass: 0
bInterfaceSubClass: 0
bInterfaceProtocol: 0
iInterface: 0
bEndpointAddress: 01h
bmAttributes: 02h
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0
bEndpointAddress: 81h
bmAttributes: 02h
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0
bEndpointAddress: 83h
bmAttributes: 02h
wMaxPacketSize: 64
bInterval: 0
bRefresh: 0
bSynchAddress: 0
==============================
And SniffUSB shows this log once the device is plugged in and
then turned off:
[0 ms] UsbSnoop compiled on Jan 18 2003 22:41:32 loading
[0 ms] UsbSnoop - DriverEntry(fc8f2c40) : Windows NT WDM version 1.32
[451 ms] UsbSnoop - AddDevice(fc8f2f50) : DriverObject ff521790, pdo ff5b8968
[691 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_PNP (0x00000018)
[691 ms] UsbSnoop - MyDispatchPNP(fc8f2ee0) : IRP_MJ_PNP (0x00000018)
[691 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_PNP (IRP_MN_QUERY_RESOURCE_REQUIREMENTS)
[691 ms] UsbSnoop - MyDispatchPNP(fc8f2ee0) : IRP_MJ_PNP (IRP_MN_QUERY_RESOURCE_REQUIREMENTS)
[691 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_PNP (IRP_MN_FILTER_RESOURCE_REQUIREMENTS)
[691 ms] UsbSnoop - MyDispatchPNP(fc8f2ee0) : IRP_MJ_PNP (IRP_MN_FILTER_RESOURCE_REQUIREMENTS)
[691 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_PNP (IRP_MN_START_DEVICE)
[691 ms] UsbSnoop - MyDispatchPNP(fc8f2ee0) : IRP_MJ_PNP (IRP_MN_START_DEVICE)
[692 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_INTERNAL_DEVICE_CONTROL
[692 ms] UsbSnoop - MyDispatchInternalIOCTL(fc8f1e80) : fdo=ff50c018, Irp=ff58e008, IRQL=0
[692 ms] >>> URB 1 going down >>>
-- URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE:
TransferBufferLength = 00000012
TransferBuffer = fc97b970
TransferBufferMDL = 00000000
Index = 00000000
DescriptorType = 00000001 (USB_DEVICE_DESCRIPTOR_TYPE)
LanguageId = 00000000
[692 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_SYSTEM_CONTROL
[696 ms] UsbSnoop - MyInternalIOCTLCompletion(fc8f1db0) : fido=00000000, Irp=ff58e008, Context=819a3db0, IRQL=2
[696 ms] <<< URB 1 coming back <<<
-- URB_FUNCTION_CONTROL_TRANSFER:
PipeHandle = ff5afa78
TransferFlags = ff9e58ff (USBD_TRANSFER_DIRECTION_IN, USBD_SHORT_TRANSFER_OK)
TransferBufferLength = 00000012
TransferBuffer = fc97b970
TransferBufferMDL = ffa53f88
00000000: 12 01 00 02 00 00 00 40 7b 16 01 01 00 00 01 02
00000010: 03 01
UrbLink = 00000000
SetupPacket =
00000000: 80 06 00 01 00 00 12 00
[696 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_INTERNAL_DEVICE_CONTROL
[696 ms] UsbSnoop - MyDispatchInternalIOCTL(fc8f1e80) : fdo=ff50c018, Irp=ff58e008, IRQL=0
[696 ms] >>> URB 2 going down >>>
-- URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE:
TransferBufferLength = 0000007c
TransferBuffer = 819cd170
TransferBufferMDL = 00000000
Index = 00000000
DescriptorType = 00000002 (USB_CONFIGURATION_DESCRIPTOR_TYPE)
LanguageId = 00000000
[701 ms] UsbSnoop - MyInternalIOCTLCompletion(fc8f1db0) : fido=00000000, Irp=ff58e008, Context=ff7a0c98, IRQL=2
[701 ms] <<< URB 2 coming back <<<
-- URB_FUNCTION_CONTROL_TRANSFER:
PipeHandle = ff5afa78
TransferFlags = ff9e58ff (USBD_TRANSFER_DIRECTION_IN, USBD_SHORT_TRANSFER_OK)
TransferBufferLength = 00000027
TransferBuffer = 819cd170
TransferBufferMDL = ffa53f88
00000000: 09 02 27 00 01 01 00 80 30 09 04 00 00 03 00 00
00000010: 00 00 07 05 01 02 40 00 00 07 05 81 02 40 00 00
00000020: 07 05 83 02 40 00 00
UrbLink = 00000000
SetupPacket =
00000000: 80 06 00 02 00 00 7c 00
[701 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_INTERNAL_DEVICE_CONTROL
[701 ms] UsbSnoop - MyDispatchInternalIOCTL(fc8f1e80) : fdo=ff50c018, Irp=ff58e008, IRQL=0
[701 ms] >>> URB 3 going down >>>
-- URB_FUNCTION_SELECT_CONFIGURATION:
ConfigurationDescriptor = 0x819cd170 (configure)
ConfigurationDescriptor : bLength = 9
ConfigurationDescriptor : bDescriptorType = 0x00000002
ConfigurationDescriptor : wTotalLength = 0x00000027
ConfigurationDescriptor : bNumInterfaces = 0x00000001
ConfigurationDescriptor : bConfigurationValue = 0x00000001
ConfigurationDescriptor : iConfiguration = 0x00000000
ConfigurationDescriptor : bmAttributes = 0x00000080
ConfigurationDescriptor : MaxPower = 0x00000030
ConfigurationHandle = 0x00000000
Interface[0]: Length = 76
Interface[0]: InterfaceNumber = 0
Interface[0]: AlternateSetting = 0
[764 ms] UsbSnoop - MyInternalIOCTLCompletion(fc8f1db0) : fido=00000000, Irp=ff58e008, Context=819248a0, IRQL=0
[764 ms] <<< URB 3 coming back <<<
-- URB_FUNCTION_SELECT_CONFIGURATION:
ConfigurationDescriptor = 0x819cd170 (configure)
ConfigurationDescriptor : bLength = 9
ConfigurationDescriptor : bDescriptorType = 0x00000002
ConfigurationDescriptor : wTotalLength = 0x00000027
ConfigurationDescriptor : bNumInterfaces = 0x00000001
ConfigurationDescriptor : bConfigurationValue = 0x00000001
ConfigurationDescriptor : iConfiguration = 0x00000000
ConfigurationDescriptor : bmAttributes = 0x00000080
ConfigurationDescriptor : MaxPower = 0x00000030
ConfigurationHandle = 0xff991960
Interface[0]: Length = 76
Interface[0]: InterfaceNumber = 0
Interface[0]: AlternateSetting = 0
Interface[0]: Class = 0x00000000
Interface[0]: SubClass = 0x00000000
Interface[0]: Protocol = 0x00000000
Interface[0]: InterfaceHandle = 0x8193a4b0
Interface[0]: NumberOfPipes = 3
Interface[0]: Pipes[0] : MaximumPacketSize = 0x00000040
Interface[0]: Pipes[0] : EndpointAddress = 0x00000001
Interface[0]: Pipes[0] : Interval = 0x00000000
Interface[0]: Pipes[0] : PipeType = 0x00000002 (UsbdPipeTypeBulk)
Interface[0]: Pipes[0] : PipeHandle = 0x8193a4cc
Interface[0]: Pipes[0] : MaxTransferSize = 0x00001000
Interface[0]: Pipes[0] : PipeFlags = 0x00000000
Interface[0]: Pipes[1] : MaximumPacketSize = 0x00000040
Interface[0]: Pipes[1] : EndpointAddress = 0x00000081
Interface[0]: Pipes[1] : Interval = 0x00000000
Interface[0]: Pipes[1] : PipeType = 0x00000002 (UsbdPipeTypeBulk)
Interface[0]: Pipes[1] : PipeHandle = 0x8193a4ec
Interface[0]: Pipes[1] : MaxTransferSize = 0x00001000
Interface[0]: Pipes[1] : PipeFlags = 0x00000000
Interface[0]: Pipes[2] : MaximumPacketSize = 0x00000040
Interface[0]: Pipes[2] : EndpointAddress = 0x00000083
Interface[0]: Pipes[2] : Interval = 0x00000000
Interface[0]: Pipes[2] : PipeType = 0x00000002 (UsbdPipeTypeBulk)
Interface[0]: Pipes[2] : PipeHandle = 0x8193a50c
Interface[0]: Pipes[2] : MaxTransferSize = 0x00001000
Interface[0]: Pipes[2] : PipeFlags = 0x00000000
[1660 ms] UsbSnoop - DispatchAny(fc8f0610) : IRP_MJ_PNP (IRP_MN_REMOVE_DEVICE)
[1660 ms] UsbSnoop - MyDispatchPNP(fc8f2ee0) : IRP_MJ_PNP (IRP_MN_REMOVE_DEVICE)
[1660 ms] UsbSnoop - RemoveDevice(fc8f2e90) : fido=ff5d0020 pdx=ff5d00d8
[1660 ms] UsbSnoop - DriverUnload(fc8f2de0) : DriverObject ff521790, IRQL=0
[1660 ms] Driver unloaded!
MyThreadFunction : myMsgCount=33 myMaxSemaphoreCount=10 myMaxIrql=2, myAllocationFailed=0, mySemaphoreFailed=0 |
|
|
|
|
codeknowbi
Joined: 22 Apr 2005
Posts: 10
Location: Phoenix,AZ
|
| Posted:
Sat May 28, 2005 7:22 pm |
|
| mconsidine wrote: |
| codeknowbi wrote: |
some interesting info from PV2Resurrector info frame
| Quote: |
878248 USB id 4146/4146, configuration 00, interface 00, alternate setting 00
Bulkout = 02 Bulkin = 81
---------------------------------SNIP----------------------------
I'm guessing that the current tools could be altered to poke at the camcorder |
I don't get anything from PV2Resurrector upon plug-in. Also, device manager is only showing me
VID=167b PID=0101
Installing the AIPTek software and changing the relevant drivers only gets me a message saying it can't start the device.
Adding a line for this VID/PID combo in the SMaL INF files and then firing up IRFANVIEW doesn't get me anywhere.
If anyone has any other thoughts on how to probe this, let me know.
(Trivia info : this is a USB 2.0 compatible device and will work without batteries but tethered to a PC) |
PV2Resurrector showed detail because I used the INFWizard form LibUSB libusb-0.1.10.1 (from the non-filter version) generate an .inf and installed. I would be curious about the low light performance of your Zoran based CVS. My Fujitsu baed one can record Moon and Stars in the same frame.
You may want to try the Cheez Movix Drivers instead, it is based on the COACH6 which should be compatible with the COACH7 in your camera. |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Sat May 28, 2005 9:22 pm |
|
Thanks for your reply. Yes, I ended up doing the same thing - ran inf_wizard under 1.10 and got a customized .inf. This allowed the Saturn to be recognized by PV2Resurrector, et. al.
Now I'm just trying to "tickle the dragon" - see how much I can screw around with it without trashing it!
I'd be happy to do a low level test for you. But right now it's raining like the dickens ...
Next step will be the Movix drivers as I couldn't get Aiptek to work. |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Sat May 28, 2005 10:19 pm |
|
| codeknowbi wrote: |
You may want to try the Cheez Movix Drivers instead, it is based on the COACH6 which should be compatible with the COACH7 in your camera. |
FWIW, I've tried installing the Coach drivers from both Movix and AIPTek. Changing the VIDs/PIDs is not getting me anywhere - in each I get an error message box saying that Windows can't start the device.
USBTool recognizes this under libusb 1.10, so that seems the most readily available route of (blind) attack. Uploading a couple of BillWs "get" and "reset" files only gets a timeout.
Also, even though it's a Zoran chip, upon power-up the first screen is a CVS screen and the second is a Pure Digital one. |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Sun May 29, 2005 11:58 am |
|
Realized I hadn't posted what this looks like to USBPoker (with libusb 1.10):
Looking at device .libusb0-0002--0x167b-0x0101
This device has 1 possible configuration(s).
Looking at configuration 0...This configuration has 1 interfaces.
Looking at interface 0...This interface has 1 altsettings.
Looking at altsetting 0...This altsetting has 3 endpoints.
Endpoint 00: Address 01h, attributes 02h (Bulk) (Out)
Endpoint 01: Address 81h, attributes 02h (Bulk) (In)
Endpoint 02: Address 83h, attributes 02h (Bulk) (In)
Opening device: .libusb0-0002--0x167b-0x0101
Opened device.
Set configuration 00.
Claimed interface 00.
Set alternate interface 00. |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Thu Jun 02, 2005 1:15 am |
|
I'm traveling right now, but if I recall, the sensor is very small and so are the lens elements. So it doesn't have something as easy to deal with as the original Dakota or the PV2s . That said, I didn't look closely at the lens system but will do that when I next get a chance. |
|
|
|
|
brite_eye
Joined: 14 Apr 2005
Posts: 2518
Location: In my dreams higher than a kite as a wingsuit flyer
|
| Posted:
Wed Jun 08, 2005 5:49 am |
|
mconsidine indicated he tried AIPTeK software - was that for camera reported in slash dot forum: "This week, Target is selling for $97 the non-disposable equivalent of this gimmick, the Aiptek "IS-DV." |
|
|
|
|
teslafreak
Joined: 04 May 2005
Posts: 105
|
| Posted:
Wed Jun 08, 2005 5:57 am |
|
not shure about the aiptek is-dv but the 4900 and 5900
use the mass storage device system for communcation
also the 5900 uses mpeg4 stating that you have twice the recording time
than the avi format used in a lot of digital cameras(a,ltough thats changing with the new models) |
|
|
|
|
mconsidine
Joined: 19 Apr 2005
Posts: 204
|
| Posted:
Wed Jun 08, 2005 12:12 pm |
|
| brite_eye wrote: |
| mconsidine indicated he tried AIPTeK software - was that for camera reported in slash dot forum: "This week, Target is selling for $97 the non-disposable equivalent of this gimmick, the Aiptek "IS-DV." |
No, I don't think that was the one. Perhaps the Aiptek's are the best avenue to pursue at the moment. I've tried getting various coach drivers recognized but always get a message saying the device couldn't be started. And throwing a variety of USB command packets at it hasn't generated any useful replies (unless I'm doing something wrong). Each comes back with a return code of -116. If that means anything to anyone, let me know!
update : it was the aiptek dv3300 software I tried ... |
|
|
|
|
Paperboy4828
Joined: 20 Apr 2005
Posts: 46
|
| Posted:
Thu Jun 09, 2005 4:34 am |
|
Just got one of the OTU video recorders from my local CVS. Man this thing is cool! Same size as a PV2 / CVS red, and the quality on the display appears to be great.
I couldn’t resist… I opened it up and took a look.  Two blobs of epoxy (one on each side) appeared to cover something the manufacturer didn’t want folks like us to have access to, so scrape, scrape, scrape… I managed to remove all the goop from both sides and still have a functioning unit. I will be posting pictures soon, but of a great deal of interest are two four “pad” areas encircled by a white box labeled J4 and J6. Could these be the areas the blobs of epoxy were trying to conceal? I have not followed the PCB to see where the circuits go, but I will try to borrow a stereo-scope from work to find out where the pads go. Also of note is the center to center measurement of the pads is the correct spacing for a standard jumper shorting cover, and it appears to have enough space to clear an installed jumper shorting cover (pretty close on one). Stay tuned… more to come! |
_________________
Sleep is for fools, who never see the sun rise! |
|
|
|
ksandbergfl
Joined: 09 Jun 2005
Posts: 66
|
| Posted:
Thu Jun 09, 2005 4:36 pm |
|
| Paperboy4828 wrote: |
I have not followed the PCB to see where the circuits go, but I will try to borrow a stereo-scope from work to find out where the pads go. Also of note is the center to center measurement of the pads is the correct spacing for a standard jumper shorting cover, and it appears to have enough space to clear an installed jumper shorting cover (pretty close on one). Stay tuned… more to come! |
Do any of the jumpers appear to be audio/video outs? I'm sure the chipset supports A/V outs, for connecting to a TV.... just need to find the right jumpers and solder in some RCA connectors. Then - you could easily transfer video to your PC by using a vidcap device.... or record the video to a VCR or DVD recorder.
I'll be getting one of these as soon as my local CVS gets them. It sounds easy enough for my 4-yr old boy to use... and for $30, it'll be a cheap way to get him interested in shooting video. |
|
|
 |
|
PanicOpticon
Joined: 09 Jun 2005
Posts: 2
|
| Posted:
Thu Jun 09, 2005 11:02 pm |
|
The pins available in J6 are exactly the same as those available above the hynix flash chip. Counting from the power connector (the one closest to it being pin 1) on J4 the 3rd pin is ground. Neither set are connected to the external connector (USB or otherwise, on the top). |
|
|
|
|
Paperboy4828
Joined: 20 Apr 2005
Posts: 46
|
| Posted:
Fri Jun 10, 2005 4:03 am |
|
Check "What Not To Do" for an update. I managed to distroy the lead from J4,3 when removing the epoxy from the display side (don't use MEK to try to soften the epoxy blob, it turns the PCB into Jello!  ). I will do one of two things with the damaged video recorder:
1) Smear some JB-Weldbond onto the PCB where the blobs used to be and return with video taken to see what the final video quality is, or...
2) Un-solder the Hynix and / or Samsung memory chips and interface with an old Lexar Jump drive to see if a NVRAM or FIRMWARE.BIN can be recovered. If there is a good guess as to whhich chip would contain such files, or where they would be located, I would be interested... |
_________________
Sleep is for fools, who never see the sun rise! |
|
|
|
Derek
Joined: 13 Jun 2005
Posts: 3
|
| Posted:
Mon Jun 13, 2005 11:30 pm |
|
|
|
|
Hill Hopper
Joined: 14 Jun 2005
Posts: 2
Location: Fayetteville, Arkansas
|
| Posted:
Tue Jun 14, 2005 1:54 am |
|
Heat will often break down epoxies. A littel heat from a 650 degree soldering station tip may knock the epoxy without damaging the chip. I don't have one of the camcorders yet so I can't verify this though at this time. (Sorry, just read this also in the "What not to do thread) |
|
|
 |
|
|
|
|
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
| |
