Post by thread:[PIC] All PIC problems solved?

Not that I'm complaining, but the list has been really light the last two days. The archives show only 19 messages each of yesterday and today. Is there some international holiday I don't know about, or has every conceivable PIC problem been solved and we should all go home now? ***************************************************************** Embed Inc, embedded system specialists in Littleton Massachusetts (978) 742-9014, http://www.embedinc.com ____________________________________________

> Not that I'm complaining, but the list has been really light the > last two days Yeah, spooky innit ? > has every conceivable PIC problem been solved and we > should all go home now ? Wondered about that last time it happened - surprised that 2000+ people seem content. I know I am for the time being ____________________________________________

Jinx wrote: >Wondered about that last time it happened - surprised that >2000+ people seem content. I know I am for the time being > Content, huh? So did you exorcise the demon that was infesting your computer? If so, how and so on... enquiring minds want to know. For what it's worth, my computer was working most peculiarly last week. It finally boiled down to a missing dll file in the /system32 dir. The effects were such that I never would have guessed that was the problem but after about a week googling, the anwer was revealed. If you are still plagued with sorrows from hell, you have my condolences. MD ____________________________________________

Well - Russell's on holiday. RP Not that I'm complaining, but the list has been really light the last two days. The archives show only 19 messages each of yesterday and today. Is there some international holiday I don't know about, or has every conceivable PIC problem been solved and we should all go home now? ____________________________________________

part 1 1038 bytes content-type:multipart/signed; protocol="application/x-pkcs7-signature"; (decoded 7bit) This is a cryptographically signed message in MIME format. --------------ms010600060406010509070707 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So what was happening? Justin. Marcel Duchamp wrote: | Jinx wrote: | |> Wondered about that last time it happened - surprised that 2000+ |> people seem content. I know I am for the time being |> | Content, huh? So did you exorcise the demon that was infesting | your computer? If so, how and so on... enquiring minds want to | know. | | For what it's worth, my computer was working most peculiarly last | week. It finally boiled down to a missing dll file in the | /system32 dir. The effects were such that I never would have | guessed that was the problem but after about a week googling, the | anwer was revealed. | | If you are still plagued with sorrows from hell, you have my | condolences. MD ______________________________________________

Justin Fielding wrote: > So what was happening? > > Justin. Not sure if you mean Jinx or me here. Jinx had some internet demon making life difficult; whether he has bannished it back to the seventh plane of hell, I can't say. For my 2 cents, my virus checker and firewall malfunctioned. This was traced to the task scheduler not running. (XP system). It would not run due to the event log program not running. That wouldn't run due to a missing dll file. A week or so before, the system had crashed and spawned chkdsk which found a bunch of errors here and there on the drive. Windows - which seemingly knows exactly which resource was asked for but failed to start - simply reports back service not running. It now seems to be better... I just noticed that Olin started this thread and that it is completely off topic at this point. So if anyone has further bits of wisdom, they should probably re-mark it as OT. MD ____________________________________________

DirecTV started the all Christmas music channel beginning of November and that always helps. Back in the good ol' days we could talk about the Christmas spirit but now I guess it's only politically correct to refer to it as the early winter retail holiday spectacular. :-( People should be easing into the holiday spirit or they're balls to the wall trying to spend budget money before the end of the calendar year. :-) > has every conceivable PIC problem been solved and we > should all go home now ? Wondered about that last time it happened - surprised that 2000+ people seem content. I know I am for the time being ____________________________________________

>-----Original Message----- >From: spam_OUTpiclist-bouncesTakeThisOuTmit.edu [.....piclist-bouncesKILLspam@spam@mit.edu] >On Behalf Of olin_piclistKILLspamembedinc.com >Sent: 16 November 2004 22:53 >To: The PIClist >Subject: [PIC] All PIC problems solved? > > >Not that I'm complaining, but the list has been really light >the last two days. The archives show only 19 messages each of >yesterday and today. Is there some international holiday I >don't know about, or has every conceivable PIC problem been >solved and we should all go home now? I had assumed the PIC mail server was having problems again! Mike ======================================================================= This e-mail is intended for the person it is addressed to only. The information contained in it may be confidential and/or protected by law. If you are not the intended recipient of this message, you must not make any use of this information, or copy or show it to any person. Please contact us immediately to tell us that you have received this e-mail, and return the original to us. Any use, forwarding, printing or copying of this message is strictly prohibited. No part of this message can be considered a request for goods or services. ======================================================================= ____________________________________________

I am working on problem reruns. The current nuisance is that MPLAB (6.6) is complaining that the path is longer than 62 characters. Error 173 I think. We have been there before, I should remember the cure. I should be able to find it in the archives, but so far, no joy. The easy workaround is to put the source directory closer to the root, but that is a cop out... BTW, so far I have not found anything to complain about using Mikropascal on a 16F628 other than it is a little clumsy to have to go to MPLAB to load the Hex to the chip. John Ferrell My Competition is not my enemy! http://DixieNC.US {Original Message removed}

{Quote hidden}> -----Original Message----- > From: .....piclist-bouncesKILLspam.....mit.edu [EraseMEpiclist-bouncesspam_OUTTakeThisOuTmit.edu]On Behalf > Of John Ferrell > Sent: 17 November 2004 15:36 > To: Microcontroller discussion list - Public. > Subject: Re: [PIC] All PIC problems solved? > > > I am working on problem reruns. > The current nuisance is that MPLAB (6.6) is complaining that the path is > longer than 62 characters. > Error 173 I think. > > We have been there before, I should remember the cure. > I should be able to find it in the archives, but so far, no joy. > > The easy workaround is to put the source directory closer to the > root, but > that is a cop out... > That's a major peeve I have with MPLAB too. I map a network drive to my project directory as a workaround (and hope any sub-directories don't extend down too far). So many development environments (not just MPLAB) don't ever seem to have been tested with anything bigger than a couple of code modules, otherwise these kinds of issues would never have got out into the wild. James ____________________________________________

Charles Craft wrote: >Back in the good ol' days we could talk about the Christmas spirit but now I guess it's only politically correct to refer to it as the early winter retail holiday spectacular. :- > > Whatever you call it, people are normally a little more generous this time of the year. Perhaps it's time to remember: http://www.piclist.com/techref/piclist/support.htm Aaron ____________________________________________

bahhhhhh humbug weeks behind....board going to layout....does have a PIC on it amongst bunches of big ASIC's and power supplies. Battling CM's that 0201 packages are good....even tho you really can't see them... And I'm just now looking at my code changes for the PIC __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ____________________________________________

is piclist still working as before? ----- Original Message ----- From: "Aaron" <piclistspam_OUTbright.net> To: "Microcontroller discussion list - Public." <@spam@piclistKILLspammit.edu> Sent: Wednesday, November 17, 2004 12:22 PM Subject: Re: [PIC] All PIC problems solved? > Charles Craft wrote: > > >Back in the good ol' days we could talk about the Christmas spirit but now I guess it's only politically correct to refer to it as the early winter retail holiday spectacular. :- > > > > > Whatever you call it, people are normally a little more generous this > time of the year. Perhaps it's time to remember: > http://www.piclist.com/techref/piclist/support.htm > > Aaron > ______________________________________________

In w98 I think the old DOS assign command works to assign a drive letter to the path? John Ferrell wrote: > I am working on problem reruns. > The current nuisance is that MPLAB (6.6) is complaining that the path is > longer than 62 characters. > Error 173 I think. > > We have been there before, I should remember the cure. > I should be able to find it in the archives, but so far, no joy. > > John Ferrell > ____________________________________________

I used 'subst' which is on all windows ;) You can type subst driveletter: path on command line and it works ;) Dave Lag wrote: {Quote hidden}> In w98 I think the old DOS assign command works to assign a drive > letter to the path? > > > John Ferrell wrote: > >> I am working on problem reruns. >> The current nuisance is that MPLAB (6.6) is complaining that the path >> is longer than 62 characters. >> Error 173 I think. >> >> We have been there before, I should remember the cure. >> I should be able to find it in the archives, but so far, no joy. >> >> John Ferrell >> > ______________________________________________

At 06:48 PM 11/17/2004 -0500, you wrote: >In w98 I think the old DOS assign command works to assign a drive letter >to the path? I use the subst command in a .bat file in my startup folder to map My Documents into a drive. It also deals with programs that have problems with spaces in paths. Best regards, Spehro Pefhany --"it's the network..." "The Journey is the reward" KILLspamspeffKILLspaminterlog.com Info for manufacturers: http://www.trexon.com Embedded software/hardware/analog Info for designers: http://www.speff.com ____________________________________________

On Wed, 17 Nov 2004 10:35:51 -0500, "John Ferrell" wrote: >I am working on problem reruns. >The current nuisance is that MPLAB (6.6) is complaining that the path is >longer than 62 characters. >Error 173 I think. > >We have been there before, I should remember the cure. >I should be able to find it in the archives, but so far, no joy. > >The easy workaround is to put the source directory closer to the root, but >that is a cop out... > Since the path length limitation is a characteristic of the .COD file format, there's not really much that can be done other than either shortening the path or suppressing .COD file generation. Regards, Bob ____________________________________________

----- Original Message ----- From: "Bob Barr" <RemoveMEbbarrTakeThisOuTcalifornia.com> Subject: Re: [PIC] All PIC problems solved? > Since the path length limitation is a characteristic of the .COD file > format, there's not really much that can be done other than either > shortening the path or suppressing .COD file generation. Well you can cheat. If you share a folder closer to your source directory, then you can create a project on that folder, rather than the actual drive. For example, I have a share at C:\Documents and Settings\John J. McDonough\My Documents\Projects Within that I have a PIC\Elmer folder I can use that share as L: and now the path to my .COD file is L:\PIC\Elmer\ which is a whole bunch shorter. --McD ____________________________________________

>>> Since the path length limitation is a characteristic of the .COD file >>> format, there's not really much that can be done other than either >>> shortening the path or suppressing .COD file generation. >> If you share a folder closer to your source directory, then you can >> create a project on that folder, rather than the actual drive. >> >> For example, I have a share at C:\Documents and Settings\John J. >> McDonough\My Documents\Projects >> >> Within that I have a PIC\Elmer folder >> >> I can use that share as L: and now the path to my .COD file is >> L:\PIC\Elmer\ which is a whole bunch shorter. > I think that was the one I was looking for! I like to keep as much as > possible in My Documents just to simplify backups. You can: - use a share. You may have to pay attention to the permissions if you are on a network. This is best for long term use, and you really should know what you're doing if you are not behind a hardware firewall like what comes with most routers. - use the subst command. This is a quickie, useful for quick one-time solutions, and doesn't have any security implications (unlike the share approach), because the subst drive is treated like a local drive. - move the whole My Documents folder with its really long path to a shorter path (right-click on the My Documents folder and set a more convenient target folder -- mine is E:\Docs\). This also allows you to keep this data on a partition that's different from your system partition, with has a number of advantages. Gerhard ____________________________________________

>Back in the good ol' days we could talk about the >Christmas spirit but now I guess it's only politically >correct to refer to it as the early winter retail >holiday spectacular. :-( Oh, you mean the annual redistibution of wealth :)) I have helped make the list a bit quieter, been off for a week on an Orcad training course. Part of the freebies from it was a natty little 4 port USB hub. ____________________________________________

----- Original Message ----- From: "Alan B. Pearce" <spamBeGoneA.B.PearcespamBeGonerl.ac.uk> Subject: Re: [PIC] All PIC problems solved? > natty little 4 port USB hub. Now there's a word I haven't heard since the first volume of The Hitchhiker's Guide. Must be that one never really made it to the colonies. --McD ____________________________________________