No exact or substring matches. trying for part
PICList
Thread
'stopped crystal'
1997\07\11@092850
by
Mal Goris
Does the CLKIN pin really have to be taken to 0 volts during ISP
programming? Or can it just be left attached to the crystal?
Mal Goris
--
http://www.nfra.nl/~mgoris/
1997\07\11@105908
by
John Payson
|
> Does the CLKIN pin really have to be taken to 0 volts during ISP
> programming? Or can it just be left attached to the crystal?
If the CPU is allowed to execute any instructions between /MClr's rise to
"+5" and its rise to "+13.5" [or more accurately, between 4v and 8v] then
programming will start not at zero, but at the instruction after the last
one executed. This will usually corrupt programming (often causing the
system to behave quite wierdly).
There are three ways to avoid this problem: [1] Keep CLKIN frozen while prog-
ramming is started. If CLKIN isn't running, the chip won't execute any
instructions. [2] Use circuitry which can pull /MClr *quickly* from VSS to
VPP (too fast for the CPU to start executing anything). If you're using
RC clock mode, I wouldn't count on this latter method working, but if you're
using a crystal the "oscillator start timer" should help you out. [3] If
you're using RC mode on a 16x84, you could enter programming mode, burn the
config fuse for another oscillator type, then reset, program the part, and
finally reburn the config for RC.
Note that a pre-burned 12C5xx may not have an oscillator input, nor a /MClr
reset. On these chips it's necessary to ensure that /MClr's rise happens
very soon after application of VDD.
1997\07\11@142816
by
www.aeug.org/~chip/
On Fri, 11 Jul 1997, John Payson wrote:
> > Does the CLKIN pin really have to be taken to 0 volts during ISP
> > programming? Or can it just be left attached to the crystal?
>
> If the CPU is allowed to execute any instructions between /MClr's rise to
> "+5" and its rise to "+13.5" [or more accurately, between 4v and 8v] then
> programming will start not at zero, but at the instruction after the last
> one executed. This will usually corrupt programming (often causing the
> system to behave quite wierdly).
An additional question: can CLKIN's level be allowed to toggle up and
down *after* programming/test mode is entered?
--Scott
/**/
1997\07\11@151212
by
John Payson
> An additional question: can CLKIN's level be allowed to toggle up and
> down *after* programming/test mode is entered?
Experience shows that the oscillator is disabled when /MCLR=VPP. I think
it likely that other code-execution tasks are disabled as well though I
may be mistaken. Are you using an externally-clocked CPU?
1997\07\11@170230
by
Andy Kunz
At 01:53 PM 7/11/97 -0500, you wrote:
>> An additional question: can CLKIN's level be allowed to toggle up and
>> down *after* programming/test mode is entered?
>
>Experience shows that the oscillator is disabled when /MCLR=VPP. I think
>it likely that other code-execution tasks are disabled as well though I
>may be mistaken. Are you using an externally-clocked CPU?
That is true so long as the rise from .8Vdd to Vpp does not take so long
that the oscillator starts running. If it starts running, then the PC will
be off by the number of cycles/4 that occurred.
Don't ask how I learned that bugaboo!
Andy
==================================================================
Andy Kunz - Montana Design - 409 S 6th St - Phillipsburg, NJ 08865
Hardware & Software for Industry & R/C Hobbies
"Go fast, turn right, and keep the wet side down!"
==================================================================
'Aargh!!! Picstart 16C programmer stopped working!'
1997\07\14@033434
by
wterreb
|
It so annoying. Just when I really needed my Picstart 16C programmer
urgently for a project I'm working on, it just stopped working. I
didn't do anything out of the ordinary with it. The last time I used
it, it was still fine, but when I tried to use it over the weekend it
just would not work anymore.
When I click on "Enable Programmer" in MPLAB, it tells me that the
device on my com port is not a Picstart16C. I already verified that
the problem does not lie with my setup, comport, cable. I even
borrowed a friend's Picstart16C and plugged into my computer to make
sure that that one works and my programmer is definetely broken.
I suppose I can return the programmed to Microchip to be fixed, but
that would take a long time and I desperately need to use it right
away. I would much rather fix it myself. Is this a standard
problem with the Picstart 16C programmers or am I the only person on
this list who have experienced this problem? Do anyone know offhand
what the problem is so I can perhaps fix it myself?
Rgds
Werner
--
Werner Terreblanche http://www.aztec.co.za/users/werner
spam_OUTwterrebTakeThisOuT
plessey.co.za (work) OR .....wernerKILLspam
@spam@aztec.co.za (home)
Plessey SA, PO Box 30451,Tokai 7966, Cape Town, South Africa
or at home : Suite 251, PostNet X5061, Stellenbosch, 7599
Tel +27 21 7102251 Fax +27 21 7102886 Home +27 21 8872196
------------------------------------------------------------
'16c55 - Stopped working'
1997\07\21@141627
by
Patrick J
I have a 16c55 that have been running for more then a year.
Yesteday I needed to make a minor change in the program.
After reprogramming with Picstart plus it dosn't work.
Now I can't get _any_ '55 to work with _any_ program !
What can have happened ?
Can the picstart plus fail to program just the 16c55 ?
It still programs my 16c74 okey.
/PJ
'[SX] Debug stopped working'
2005\09\05@105854
by
Electronegativityn/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Electronegativity wrote:The debug feature has stopped working. :cry:
All the memory loactions are zero and it claims to be running.
The SX key still programs the chips.
Could I have somehow damages one of the oscillator inputs?
What should I do?
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\05@184611
by
Stuart Whiten/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Stuart White wrote:Did you add a resonator or crystal to your circuit recently. I remember reading that they will disable debugging capability.
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87047
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\05@185854
by
Electronegativityn/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Electronegativity wrote:No, it happens with only the SX28 plugged into the SXTech board and running a memory manipulation example program from Gunther's book.
All the values read zero, and the 0th program location is highlighted in the debugger instead of the jump instruction at the very end.
Maybe I somehow fried something in the SX key, but it still programs the chips properly; it's just that the debugger doesn't work anymore.
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87049
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\06@092133
by
PJMontyn/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, PJMonty wrote:Electronegativity,
Do you have a few SX chips? If so, does it do it with all the chips or just one of them?
[list]Thanks,
PeterM[/list]
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87109
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\06@094636
by
Electronegativityn/a
|
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Electronegativity wrote:All of them.
I have an SX28 on the Parallax SXTech board, an SX18 on a breadboard, and another SX18 on a prototype board.
The debugger was working fine on Saturday, then it was not working Sunday morning.
I will re-install it when I get home.
The reason I posted this thread was to find out if it is possible to damage the SXkey in such a way that it would be able to program the chips, but would no longer communicate with the debugger.
My soldering technique is still very poor, and there have been a few short circuits.
What if one of the oscillator pins was exposed to a 5V input?
Could that have caused the problem?
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87112
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\06@162939
by
PJMontyn/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, PJMonty wrote:Electronegativity,
I have found the SxKey to be pretty robust, but it's always possible that you damaged it. Sounds like a call to tech support may be in order.
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87167
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\06@213442
by
Electronegativityn/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Electronegativity wrote:I guess I'l send an email off to tech support then, because reinstalling the software didn't help.
What's really odd is that the device is capable of both programming the chips and reading the memory of a programmed chip from the run->device->read button.
When the debugger starts the line that designates the reset direction is highlighted instead of the jump at the end of the universe, and all the registers read zero. The box on the upper left says "running" and all the buttons except reset and reset pos are greyed out.
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87188
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\06@221353
by
PJMontyn/a
|
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, PJMonty wrote:Electronegativity,
By any chance are you using the "Debug (reenter)" command instead of just "Debug"? If so, are you sure that the last time you programmed the chip it was programmed via "Debug" and not via "Program"?
When you choose Run->Program, it just programs the chip with your code. This is what you do when your code is finalized and you want to program a chip to run in standalone mode.
When you choose Run->Debug, it program the chip with your code and with the code needed for the SxKey to enable and control the debugging.
If you do Run->Program (or Ctrl-P) and then do Run->Debug (reenter) (or Ctrl-AltD) the debug window will say "Running", the buttons will be greyed out, and the "Reset" line will be highlighted blue.
The Debug (reenter) should only be used when you have previously programmed the chip via "Debug" and simply want to jump into and debug the code that is already in the flash memory of the SX.
[list]Thanks,
PeterM[/list]
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87189
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\07@013414
by
g_daubachn/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, g_daubach wrote:Electronegativity,
I have several SX-Keys here. One of them shows exactly the symptom you describe, i.e. I can use it for programming SXes but when I activate the debugger, it always comes up in Running mode. When I replace the SX-Key, I can enter the debugger as usual without the need to re-program the chip that was programmed with the "Run-only" SX-Key before. IOW, this one I have here is definitely broken.
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87194
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\07@070336
by
Electronegativityn/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Electronegativity wrote:Hi Gunther, do you have any idea how it could have happened?
I guess I will have to buy another one, but I don't want to break this one too.
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87200
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\07@104503
by
g_daubachn/a
|
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, g_daubach wrote:Hi Electronegativity,
sorry, I don't have a clue what (partly) killed one of my SX-Keys. In general, the SX-Key is quite robust. It happened to me more than once that I attached one to the programming 4-pin header in wrong orientation. Once, due some bad wiring, an external heavy 24V power supply drove over 10 Amps through the ground pin, the SUB-D 9 connector, the serial cable to the PC's ground and back to the power supply. I only recognized this when my serial cable became hot. This actually damaged the serial cable but the SK-Key survived!
Maybe, some electrostatic discharge caused the damage. Normally, I only plug/unplug the SX-Key with the power supply turned off, and I try to "unload" myself by touching ground potential before handling the SX-Key but you never know...
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87236
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\07@114455
by
Electronegativityn/a
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Electronegativity wrote:Ok thanks, I guess that's it then.
I sent off an email to Parallax tech support to find out if there are any options for repairing or replacing it.
Also, I really like the SXSim.
It would be awesomely useful if the debugger gave as much information as the simulation does.
---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87239
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
2005\09\07@145407
by
g_daubachn/a
|
In SX Microcontrollers, SX/B Compiler and SX-Key Tool, g_daubach wrote:[Quoting: "Electronegativity"]Ok thanks, I guess that's it then.
I sent off an email to Parallax tech support to find out if there are any options for repairing or replacing it.
Also, I really like the SXSim.
It would be awesomely useful if the debugger gave as much information as the simulation does.
I'm glad that you like SXSim. With a simulator, you can always implement features that can't be available with the debugger. The SX-Key IDE can only display the information that it can retrieve from the SX chip under test. Nevertheless, the Debugger has the great advantage that it allows you to execute code in real-time where for a simulator it is hard to match that speed, but I'm working on it :-) .---------- End of Message ----------
You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=86998#m87269
Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com
The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)
'[OT][ADMIN] The list has stopped coming once again'
2006\10\09@102415
by
Attila Muhi
Hi list,
So, now I don't receive postings from the list. Again ....
I've verified my list options any they seems to be set correctly. And my ISP
doesn't filter out anything....
What to do ? ;.-(
Best regards
Attila - SM4RAN
{Original Message removed}
2006\10\09@132914
by
James Newtons Massmind
Your ISP is lying.
---
James.
{Quote hidden}> -----Original Message-----
> From:
piclist-bounces
KILLspammit.edu
> [
.....piclist-bouncesKILLspam
.....mit.edu] On Behalf Of Attila Muhi
> Sent: 2006 Oct 09, Mon 07:19
> To: Microcontroller discussion list - Public.
> Subject: [OT][ADMIN] The list has stopped coming once again...
>
> Hi list,
>
> So, now I don't receive postings from the list. Again ....
>
> I've verified my list options any they seems to be set
> correctly. And my ISP doesn't filter out anything....
>
> What to do ? ;.-(
>
> Best regards
>
> Attila - SM4RAN
>
>
> ----- Original Message -----
> From: "Howard Winter" <
EraseMEHDRWspam_OUT
TakeThisOuTH2Org.demon.co.uk>
> To: "Microcontroller discussion list - Public." <
piclist
spam_OUTmit.edu>
> Sent: Monday, September 04, 2006 3:44 PM
> Subject: Re: [EE] charging a 12V battery with solar array
>
>
> > Russell,
> >
> > On Sun, 03 Sep 2006 14:38:52 +1200, Russell McMahon wrote:
> >
> > > > Here is a charger idea that is interesting:
> > > >
> > > >
http://www.tunecharger.com/
> > >
> > > Not overly cheap.
> > > PIC16F675 based boost converter
> > > Circuit on page 10.
> > >
> > >
> www.tunecharger.com/2006_t_0001_mtc_3-330.2%20%20reva%2
0technical%20r
{Quote hidden}> eference%20manual.pdf.
> >
> > By a strange coincidence I found the above recently (have you been
> > hacking
> my gargoyle [tm] searches? :-)
> >
> > It is interesting, but it's too puny for what I need: 24V battery
> > system
> (so open-circuit voltage of solar array will be up in the
> 30s), at least 10A
> > charging current - preferably more. I did wonder about
> scaling this
> > up,
> but a number of the components are something of a mystery to me -
> > especially the MOSFET driver chip - not sure how its characteristics
> affect the specs for the whole unit. Obviously the 7805 is
> the first thing that
> > won't stand 30V+ across it, but which components result in the 10W
> > power
> limit I don't know. It's all a but non-digital, an area in
> which I am never
> > comfortable! :-)
> >
> > Cheers,
> >
> >
> > Howard Winter
> > St.Albans, England
> >
> >
> > --
2006\10\09@135547
by
Mitch Miller
Or is misconfigured ... I had an issue for a while where of my name
servers was not responding and mail from Yahoo, PayPal and the Piclist
quit coming through (even though mail from other sources, including
GMail, my employer and many individuals was still being delivered
successfully).
Once my secondary name server came back up, it all started working again
(sorta makes you wonder why you HAVE TO have two name servers).
-- Mitch
James Newtons Massmind wrote:
> Your ISP is lying.
>
> ---
> James.
>
>
>
>
>>{Original Message removed}
'[OT]: games people play (or how I stopped worrying'
2008\10\12@230927
by
M. Adam Davis
So many of you know I'm competing in a PIC32 contest (please vote!):
http://mypic32.com/web/guest/contestantsprofiles?profileID=50331
and have thought of a few games that kids can play on the device, but
was thinking about games people could play together with the device.
As I was discussing it with a friend who mentioned Capture the Flag, I
though this could be an interesting device to change old games.
Incorprating games into the device itself is very important for child
acceptance - they won't want to carry something that not only provides
them minimal functionality, but also allows greater parental
oversight.
So an enhanced version of capture the flag might involve no flag at
all. You lay out the boundaries of the play space by walking them
while the unit records, and then specify a flag station for each team.
If you walk into the flag station of an enemy team then your device
captures the flag automatically, and the enemy team is alerted as you
try to run away. You might be able to pass the flag onto another team
mate, enact jails, spies, etc. You can see where your teammates are,
and in certain version of the game your position might be made known
to the enemy if you have the flag.
Such a device (ie, 802.15.4 mesh network, GPS, compass, display) can
probably be used to change the way many games are played.
So what games do you think could be enhanced with this toy?
-Adam
--
Save Money * Save Oil * Save Lives * Save the Planet
http://www.driveslowly.org
2008\10\13@125919
by
Sean Breheny
Hi Adam,
Looks really cool. However, are you depending on Zigbee for comms?
That has a typical range of only 100 meters (unless you go with the
higher powered version, but that still would be rather limited I'd
think).
Sean
On Sun, Oct 12, 2008 at 11:09 PM, M. Adam Davis <@spam@stienmanKILLspam
gmail.com> wrote:
{Quote hidden}> So many of you know I'm competing in a PIC32 contest (please vote!):
>
>
http://mypic32.com/web/guest/contestantsprofiles?profileID=50331
>
> and have thought of a few games that kids can play on the device, but
> was thinking about games people could play together with the device.
>
> As I was discussing it with a friend who mentioned Capture the Flag, I
> though this could be an interesting device to change old games.
> Incorprating games into the device itself is very important for child
> acceptance - they won't want to carry something that not only provides
> them minimal functionality, but also allows greater parental
> oversight.
>
> So an enhanced version of capture the flag might involve no flag at
> all. You lay out the boundaries of the play space by walking them
> while the unit records, and then specify a flag station for each team.
> If you walk into the flag station of an enemy team then your device
> captures the flag automatically, and the enemy team is alerted as you
> try to run away. You might be able to pass the flag onto another team
> mate, enact jails, spies, etc. You can see where your teammates are,
> and in certain version of the game your position might be made known
> to the enemy if you have the flag.
>
> Such a device (ie, 802.15.4 mesh network, GPS, compass, display) can
> probably be used to change the way many games are played.
>
> So what games do you think could be enhanced with this toy?
>
> -Adam
>
> --
> Save Money * Save Oil * Save Lives * Save the Planet
>
http://www.driveslowly.org
> -
2008\10\13@132438
by
M. Adam Davis
Unamplified and under excellent outdoor conditions, the Microchip
module has up to a 400m range (1/4 mile) (according to microchip, of
course. I'm doing testing on this and other modules as needed in the
near future). That, and the fact that it's low power drew me towards
this solution, but testing will show whether it's really that good.
But yes, this design is meant for short range. Once it forms a mesh
network, however, in a largish group its effective range is much
larger - which would be the case for games such as capture the flag.
This is large enough to communicate in an open play area of over 150
acres square, if the parent is in the middle, or if a repeater node is
placed near the middle - again under ideal conditions.
I expect to get a few hundred feet from it under average conditions,
which will take care of most situations involving children of the age
group this is meant for. For larger areas it will significantly
decrease search time - you would only need to walk around a bit until
you get a signal, and then follow it. A repeater could be made if
this was a requested feature (especially if they wanted to keep RF
energy for handheld or body worn units)
For games, though, it'll involve many more people, and a robust mesh
network will significantly extend the effective range.
Of course, if this does become a commercial product I'll also
integrate cellular modules into various versions for longer distance
and more robust tracking, but that's not the primary market.
-Adam
On Mon, Oct 13, 2008 at 12:59 PM, Sean Breheny <KILLspamshb7KILLspam
cornell.edu> wrote:
{Quote hidden}> Hi Adam,
>
> Looks really cool. However, are you depending on Zigbee for comms?
> That has a typical range of only 100 meters (unless you go with the
> higher powered version, but that still would be rather limited I'd
> think).
>
> Sean
>
>
> On Sun, Oct 12, 2008 at 11:09 PM, M. Adam Davis <
RemoveMEstienmanTakeThisOuT
gmail.com> wrote:
>> So many of you know I'm competing in a PIC32 contest (please vote!):
>>
>> mypic32.com/web/guest/contestantsprofiles?profileID=50331
>>
>> and have thought of a few games that kids can play on the device, but
>> was thinking about games people could play together with the device.
>>
>> As I was discussing it with a friend who mentioned Capture the Flag, I
>> though this could be an interesting device to change old games.
>> Incorprating games into the device itself is very important for child
>> acceptance - they won't want to carry something that not only provides
>> them minimal functionality, but also allows greater parental
>> oversight.
>>
>> So an enhanced version of capture the flag might involve no flag at
>> all. You lay out the boundaries of the play space by walking them
>> while the unit records, and then specify a flag station for each team.
>> If you walk into the flag station of an enemy team then your device
>> captures the flag automatically, and the enemy team is alerted as you
>> try to run away. You might be able to pass the flag onto another team
>> mate, enact jails, spies, etc. You can see where your teammates are,
>> and in certain version of the game your position might be made known
>> to the enemy if you have the flag.
>>
>> Such a device (ie, 802.15.4 mesh network, GPS, compass, display) can
>> probably be used to change the way many games are played.
>>
>> So what games do you think could be enhanced with this toy?
>>
>> -Adam
>>
>> --
>> Save Money * Save Oil * Save Lives * Save the Planet
>>
http://www.driveslowly.org
>> --
'[OT]: Zip when it moved and pop when it stopped...'
2009\01\05@132305
by
M. Adam Davis
On Mon, Jan 5, 2009 at 9:41 AM, Vitaliy <spamBeGonespamspamBeGone
maksimov.org> wrote:
> "M. Adam Davis" wrote:
>> As far as my original problem, I ended up buying a train and car with
>> sounds, and putting the train module inside the car (left the car PCB
>> in there as well for the button).
>>
>> He was pleased to receive the car that went choo-choo, as he had
>> requested from two different santas. And it took me about an hour
>> (the car was glued together. Grrr....) which is a lot less time than
>> it would have taken to do the sound myself.
>
> Adam, you're spoiling your son rotten! :-)
:-D
Now I just need to make one of these:
http://www.mydfz.com/Paxton/lyrics/tmt.htm
My Wife's family likes that song...
-Adam
--
Please rate and vote for my contest entry:
mypic32.com/web/guest/profiles?profileID=50331
2009\01\05@140009
by
William \Chops\ Westfield
2009\01\05@140921
by
M. Adam Davis
'[OT] i have stopped receiving my own postings'
2009\08\16@133446
by
AGSCalabrese
these are the ones I love the most. I did not change my settings and
I checked
and I still am enabled to receive my own very best musings.
Gus
2009\08\16@140401
by
Carl Denk
Message received here :)
AGSCalabrese wrote:
> these are the ones I love the most. I did not change my settings and
> I checked
> and I still am enabled to receive my own very best musings.
>
> Gus
>
2009\08\16@203920
by
Bob Blick
AGSCalabrese wrote:
> these are the ones I love the most. I did not change my settings and
> I checked
> and I still am enabled to receive my own very best musings.
This is a well-know bug/feature of gmail. Google would let you see your
own messages but they know best, right?
Cheerful regards,
Bob
2009\08\16@205346
by
AGSCalabrese
Ah yes thanks for reminding me Bob
Gus
On Aug 16, 2009, at 6:39 PM, Bob Blick wrote:
AGSCalabrese wrote:
> these are the ones I love the most. I did not change my settings and
> I checked
> and I still am enabled to receive my own very best musings.
This is a well-know bug/feature of gmail. Google would let you see your
own messages but they know best, right?
Cheerful regards,
Bob
2009\08\16@232413
by
Sean Breheny
Hmmm. I use gmail and don't have a problem with this. What specific
issue are you talking about? It could be because I post to the list
with an non-gmail email alias, which then re-directs mail to my gmail
account.
Sean
On Sun, Aug 16, 2009 at 8:39 PM, Bob Blick<RemoveMEbobblick
TakeThisOuTftml.net> wrote:
{Quote hidden}> AGSCalabrese wrote:
>> these are the ones I love the most. I did not change my settings and
>> I checked
>> and I still am enabled to receive my own very best musings.
>
>
> This is a well-know bug/feature of gmail. Google would let you see your
> own messages but they know best, right?
>
> Cheerful regards,
>
> Bob
>
2009\08\17@000623
by
Bob Blick
Sean Breheny wrote:
> Hmmm. I use gmail and don't have a problem with this. What specific
> issue are you talking about? It could be because I post to the list
> with an non-gmail email alias, which then re-directs mail to my gmail
> account.
Well, I suppose if I use a hammer as a paperweight that still counts as
using a hammer, but typically when one refers to using a hammer I assume
they use it for hammering.
So when I referred to gmail I meant gmail, the normal use of gmail,
posting and receiving with gmail using a gmail email address, not the
way you use gmail, which isn't. :)
Best regards,
Bob
2009\08\17@010258
by
Xiaofan Chen
On Mon, Aug 17, 2009 at 1:34 AM, AGSCalabrese<agscalEraseME
.....gmail.com> wrote:
> these are the ones I love the most. I did not change my settings and
> I checked and I still am enabled to receive my own very best musings.
>
If you are the OP and nobody replies, it will only be in the Sent Mail
folder. If you are not the OP, it should still be in your inbox.
If you have set up a proper filter to add a label (say PIClist)
for the PIClist, they should all be labeled correctly. Gmail
makes it very easy to filter mailing list. I use Gmail for
all the mailing lists and it is very good at threading.
--
Xiaofan http://mcuee.blogspot.com
2009\08\17@131520
by
AGSCalabrese
I do not use gmail as my client.... I only use it as a server.
I never go look at the Gmail folders.
Gus
{Quote hidden}>
> On Aug 16, 2009, at 11:02 PM, Xiaofan Chen wrote:
>
> On Mon, Aug 17, 2009 at 1:34 AM, AGSCalabrese<
EraseMEagscal
gmail.com> wrote:
>> these are the ones I love the most. I did not change my settings and
>> I checked and I still am enabled to receive my own very best musings.
>>
>
> If you are the OP and nobody replies, it will only be in the Sent Mail
> folder. If you are not the OP, it should still be in your inbox.
>
> If you have set up a proper filter to add a label (say PIClist)
> for the PIClist, they should all be labeled correctly. Gmail
> makes it very easy to filter mailing list. I use Gmail for
> all the mailing lists and it is very good at threading.
>
> --
> Xiaofan
http://mcuee.blogspot.com
>
> -
'p1.exe has stopped working'
2010\06\18@105556
by
David Novak
|
I have the following setup:
HI Tech PICC 8.02PL1
MPLAB v8.53
Windows 7
When I build, I get the message "p1.exe has stopped working". Does
anyone know how to solve this issue?
I can build on the command line without any problems and I could live
with building on the command line, but I've not been able to get MPLAB
to step through the source code using the ICD2. If I import the hex
file, it steps through the disassembled Program Memory just fine, but I
want to step through the C source code. If I build on the command line,
can I still debug at the C source code level?
The build output for the p1.exe crash is provided below.
Thanks,
David
----
Clean: Deleting intermediary and output files.
Clean: Deleted file "C:\source\startup.obj".
Clean: Deleted file "C:\source\startup.ase".
Clean: Deleted file "C:\source\dp4.obj".
Clean: Deleted file "C:\source\dp4.cce".
Clean: Deleted file "C:\source\DP4.mcs".
Clean: Done.
Executing: "C:\HT-PIC\BIN\PICC.EXE" -C -E"startup.ase" "startup.as"
-O"startup.obj" -Q -MPLAB -16F877 -ICD -V -O -X
aspic.exe -v -x -E1 -EC:\Users\David\AppData\Local\Temp\_498.AAA -o
-R2000 -CC:\HT-PIC\LIB\picinfo.ini -16F877 -ver=V8.02PL1 -icd
-ostartup.obj startup.as
del C:\Users\David\AppData\Local\Temp\_498.AAA
del C:\Users\David\AppData\Local\Temp\_498.AAB
del C:\Users\David\AppData\Local\Temp\_498.AAC
del C:\Users\David\AppData\Local\Temp\_498.AAD
del l.obj
del C:\Users\David\AppData\Local\Temp\_498.AAE
Executing: "C:\HT-PIC\BIN\PICC.EXE" -C -E"dp4.cce" "dp4.c" -O"dp4.obj"
-Q -MPLAB -16F877 -ICD -V -Zg1 -O -X
clist.exe dp4.c dp4.lst
cpp.exe -DHI_TECH_C -D_MPC_ -SP1,1,1,1,1,1,1 -IC:\HT-PIC\INCLUDE
-S1,2,2,4,3,3 -E1 -EC:\Users\David\AppData\Local\Temp\_1P0.AAA -D_16F877
-D_PIC14 -D_COMMON_=1 -DMPLAB_ICD -D_PROGMEM_=2 -D_HTC_VER_MAJOR_=8
-D_HTC_VER_MINOR_=2 -D_HTC_VER_PATCH_=1 -D_BANKBITS_=2 -D_GPRBITS_=2
C:\dp4_tc\source\dp4.c C:\Users\David\AppData\Local\Temp\_1P0.AAB
p1.exe -E1 -EC:\Users\David\AppData\Local\Temp\_1P0.AAA -D -M -B
-QTi,fastcall -QX,bank1 -QY,bank2 -QZ,bank3 -Gstrings,const -Y -r -u
C:\Users\David\AppData\Local\Temp\_1P0.AAB
C:\Users\David\AppData\Local\Temp\_1P0.AAC
C:\Users\David\AppData\Local\Temp\_1P0.AAD
del C:\Users\David\AppData\Local\Temp\_1P0.AAA
del C:\Users\David\AppData\Local\Temp\_1P0.AAB
del C:\Users\David\AppData\Local\Temp\_1P0.AAC
del C:\Users\David\AppData\Local\Temp\_1P0.AAD
del l.obj
del C:\Users\David\AppData\Local\Temp\_1P0.AAE
The instruction at 0040918b referenced memory at 2e315f77
The memory could not be read fromHalting build on first failure as
requested.
BUILD FAILED: Fri Jun 18 10:44:29 2010
2010\06\18@164106
by
Barry Gershenfeld
|
In my experience, there's a lot of software between MPLAB and the running of
any given compiler. The crash looks like an exception from deep within the
language runtime, which generally means that while there is a bug somewhere,
that kind of information isn't going to help us fix anything.
What I've found, though, on many occasions is, the problem is extremely
sensitive to the current working environment and any change at all will make
the problem go away. So try the following.
-Try it again.
-Change something in the source code and try again.
-Close MPLAB, then run it again and try again.
-Reboot and try again.
-Create a new project with a different name, include the source code, and
try again.
Usually I reverse the last two steps, because it usually is something in the
project file, plus my project files are pretty simple, and I can make a new
one faster than I can reboot.
==Take Two==
There is one other thought I had. I used to be able to crash the CCS
compiler by invoking certain library functions where I hadn't included the
appropriate .h file. So, sometimes it actually is the source code's fault.
In that case it's good to ask "What did I just change?" and go back to a
previous version, if that option is available. And one more thought...try
building some other project, just to test the sanity of the MPLAB+compiler
setup.
2010\06\18@191612
by
David Novak
|
I have the following setup:
HI Tech PICC 8.02PL1
MPLAB v8.53
Windows 7
When I build, I get the message "p1.exe has stopped working". Does
anyone know how to solve this issue?
I can build on the command line without any problems and I could live
with building on the command line, but I've not been able to get MPLAB
to step through the source code using the ICD2. If I import the hex
file, it steps through the disassembled Program Memory just fine, but I
want to step through the C source code. If I build on the command line,
can I still debug at the C source code level?
The build output for the p1.exe crash is provided below.
Thanks,
David
----
Clean: Deleting intermediary and output files.
Clean: Deleted file "C:\source\startup.obj".
Clean: Deleted file "C:\source\startup.ase".
Clean: Deleted file "C:\source\dp4.obj".
Clean: Deleted file "C:\source\dp4.cce".
Clean: Deleted file "C:\source\DP4.mcs".
Clean: Done.
Executing: "C:\HT-PIC\BIN\PICC.EXE" -C -E"startup.ase" "startup.as"
-O"startup.obj" -Q -MPLAB -16F877 -ICD -V -O -X
aspic.exe -v -x -E1 -EC:\Users\David\AppData\Local\Temp\_498.AAA -o
-R2000 -CC:\HT-PIC\LIB\picinfo.ini -16F877 -ver=V8.02PL1 -icd
-ostartup.obj startup.as
del C:\Users\David\AppData\Local\Temp\_498.AAA
del C:\Users\David\AppData\Local\Temp\_498.AAB
del C:\Users\David\AppData\Local\Temp\_498.AAC
del C:\Users\David\AppData\Local\Temp\_498.AAD
del l.obj
del C:\Users\David\AppData\Local\Temp\_498.AAE
Executing: "C:\HT-PIC\BIN\PICC.EXE" -C -E"dp4.cce" "dp4.c" -O"dp4.obj"
-Q -MPLAB -16F877 -ICD -V -Zg1 -O -X
clist.exe dp4.c dp4.lst
cpp.exe -DHI_TECH_C -D_MPC_ -SP1,1,1,1,1,1,1 -IC:\HT-PIC\INCLUDE
-S1,2,2,4,3,3 -E1 -EC:\Users\David\AppData\Local\Temp\_1P0.AAA -D_16F877
-D_PIC14 -D_COMMON_=1 -DMPLAB_ICD -D_PROGMEM_=2 -D_HTC_VER_MAJOR_=8
-D_HTC_VER_MINOR_=2 -D_HTC_VER_PATCH_=1 -D_BANKBITS_=2 -D_GPRBITS_=2
C:\dp4_tc\source\dp4.c C:\Users\David\AppData\Local\Temp\_1P0.AAB
p1.exe -E1 -EC:\Users\David\AppData\Local\Temp\_1P0.AAA -D -M -B
-QTi,fastcall -QX,bank1 -QY,bank2 -QZ,bank3 -Gstrings,const -Y -r -u
C:\Users\David\AppData\Local\Temp\_1P0.AAB
C:\Users\David\AppData\Local\Temp\_1P0.AAC
C:\Users\David\AppData\Local\Temp\_1P0.AAD
del C:\Users\David\AppData\Local\Temp\_1P0.AAA
del C:\Users\David\AppData\Local\Temp\_1P0.AAB
del C:\Users\David\AppData\Local\Temp\_1P0.AAC
del C:\Users\David\AppData\Local\Temp\_1P0.AAD
del l.obj
del C:\Users\David\AppData\Local\Temp\_1P0.AAE
The instruction at 0040918b referenced memory at 2e315f77
The memory could not be read fromHalting build on first failure as
requested.
BUILD FAILED: Fri Jun 18 10:44:29 2010
2010\06\19@043636
by
Tamas Rudnai
Hi David,
You need to add a tag to subject otherwise many people here would not be
able to see your message. You have posted it twice, I believe that is
because neither you saw your own post, so you might thought your message got
rejected?
Anyway, added [PIC] tag...
Tamas
---------- Forwarded message ----------
From: David Novak <RemoveMEDavid.NovakEraseME
EraseMEdajac.com>
Date: Sat, Jun 19, 2010 at 12:16 AM
Subject: p1.exe has stopped working
To: RemoveMEpiclistspam_OUT
KILLspammit.edu
I have the following setup:
HI Tech PICC 8.02PL1
MPLAB v8.53
Windows 7
When I build, I get the message "p1.exe has stopped working". Does
anyone know how to solve this issue?
I can build on the command line without any problems and I could live
with building on the command line, but I've not been able to get MPLAB
to step through the source code using the ICD2. If I import the hex
file, it steps through the disassembled Program Memory just fine, but I
want to step through the C source code. If I build on the command line,
can I still debug at the C source code level?
The build output for the p1.exe crash is provided below.
Thanks,
David
----
Clean: Deleting intermediary and output files.
Clean: Deleted file "C:\source\startup.obj".
Clean: Deleted file "C:\source\startup.ase".
Clean: Deleted file "C:\source\dp4.obj".
Clean: Deleted file "C:\source\dp4.cce".
Clean: Deleted file "C:\source\DP4.mcs".
Clean: Done.
Executing: "C:\HT-PIC\BIN\PICC.EXE" -C -E"startup.ase" "startup.as"
-O"startup.obj" -Q -MPLAB -16F877 -ICD -V -O -X
aspic.exe -v -x -E1 -EC:\Users\David\AppData\Local\Temp\_498.AAA -o
-R2000 -CC:\HT-PIC\LIB\picinfo.ini -16F877 -ver=V8.02PL1 -icd
-ostartup.obj startup.as
del C:\Users\David\AppData\Local\Temp\_498.AAA
del C:\Users\David\AppData\Local\Temp\_498.AAB
del C:\Users\David\AppData\Local\Temp\_498.AAC
del C:\Users\David\AppData\Local\Temp\_498.AAD
del l.obj
del C:\Users\David\AppData\Local\Temp\_498.AAE
Executing: "C:\HT-PIC\BIN\PICC.EXE" -C -E"dp4.cce" "dp4.c" -O"dp4.obj"
-Q -MPLAB -16F877 -ICD -V -Zg1 -O -X
clist.exe dp4.c dp4.lst
cpp.exe -DHI_TECH_C -D_MPC_ -SP1,1,1,1,1,1,1 -IC:\HT-PIC\INCLUDE
-S1,2,2,4,3,3 -E1 -EC:\Users\David\AppData\Local\Temp\_1P0.AAA -D_16F877
-D_PIC14 -D_COMMON_=1 -DMPLAB_ICD -D_PROGMEM_=2 -D_HTC_VER_MAJOR_=8
-D_HTC_VER_MINOR_=2 -D_HTC_VER_PATCH_=1 -D_BANKBITS_=2 -D_GPRBITS_=2
C:\dp4_tc\source\dp4.c C:\Users\David\AppData\Local\Temp\_1P0.AAB
p1.exe -E1 -EC:\Users\David\AppData\Local\Temp\_1P0.AAA -D -M -B
-QTi,fastcall -QX,bank1 -QY,bank2 -QZ,bank3 -Gstrings,const -Y -r -u
C:\Users\David\AppData\Local\Temp\_1P0.AAB
C:\Users\David\AppData\Local\Temp\_1P0.AAC
C:\Users\David\AppData\Local\Temp\_1P0.AAD
del C:\Users\David\AppData\Local\Temp\_1P0.AAA
del C:\Users\David\AppData\Local\Temp\_1P0.AAB
del C:\Users\David\AppData\Local\Temp\_1P0.AAC
del C:\Users\David\AppData\Local\Temp\_1P0.AAD
del l.obj
del C:\Users\David\AppData\Local\Temp\_1P0.AAE
The instruction at 0040918b referenced memory at 2e315f77
The memory could not be read fromHalting build on first failure as
requested.
BUILD FAILED: Fri Jun 18 10:44:29 2010
2010\06\19@083218
by
RussellMc
Please add [PIC] tag if replying to this thread.
2010\06\19@172351
by
John Temples
> I have the following setup:
>
> HI Tech PICC 8.02PL1
> MPLAB v8.53
> Windows 7
>
> When I build, I get the message "p1.exe has stopped working". Does
> anyone know how to solve this issue?
Was this working with a previous version of MPLAB IDE? Why are you
using such an old version of the compiler? I don't know how
compatible the recent MPLAB IDE language plugins would be with this
version.
> I can build on the command line without any problems and I could live
> with building on the command line, but I've not been able to get MPLAB
> to step through the source code using the ICD2. If I import the hex
> file, it steps through the disassembled Program Memory just fine, but I
> want to step through the C source code. If I build on the command line,
> can I still debug at the C source code level?
You need to import the .COF file for debugging (or given the age of
the compiler, it might be a .COD file).
--
John W. Temples, III
2010\06\20@002838
by
David Novak
> Was this working with a previous version of MPLAB IDE? Why are you
> using such an old version of the compiler? I don't know how
> compatible the recent MPLAB IDE language plugins would be with this
> version.
This is an old project that needs a small number of changes. The build
works on a different computer with this compiler and MPLAB v8.5 and
Windows XP. I started with v8.5, but it had the same failure, so I
upgraded to 8.53 to see of that would fix the problem, but it didn't
help.
>
> You need to import the .COF file for debugging (or given the age of
> the compiler, it might be a .COD file).
I did import the cof, but it acts the same as importing the hex.
Should the C file automatically open and show the execution point when
I halt execution and single step?
Thanks,
David
2010\06\20@175507
by
John Temples
On Sun, 20 Jun 2010, David Novak wrote:
>> You need to import the .COF file for debugging (or given the age of
>> the compiler, it might be a .COD file).
>
> I did import the cof, but it acts the same as importing the hex.
> Should the C file automatically open and show the execution point when
> I halt execution and single step?
Yes.
--
John W. Temples, III
2010\06\23@095108
by
David Novak
I found the issue... The path to my source code was too long. After
reducing the path, the project builds without error and I'm able to
debug at the source code level.
David
On 6/20/2010 5:55 PM, John Temples wrote:
{Quote hidden}> On Sun, 20 Jun 2010, David Novak wrote:
>
>
>>> You need to import the .COF file for debugging (or given the age of
>>> the compiler, it might be a .COD file).
>>>
>> I did import the cof, but it acts the same as importing the hex.
>> Should the C file automatically open and show the execution point when
>> I halt execution and single step?
>>
> Yes.
>
> --
> John W. Temples, III
>
2010\06\23@101213
by
Jan-Erik Soderholm
How long is "too long" ?
And is/was this documented ?
On 2010-06-23 15:51, David Novak wrote:
{Quote hidden}> I found the issue... The path to my source code was too long. After
> reducing the path, the project builds without error and I'm able to
> debug at the source code level.
>
> David
>
>
> On 6/20/2010 5:55 PM, John Temples wrote:
>> On Sun, 20 Jun 2010, David Novak wrote:
>>
>>
>>>> You need to import the .COF file for debugging (or given the age of
>>>> the compiler, it might be a .COD file).
>>>>
>>> I did import the cof, but it acts the same as importing the hex.
>>> Should the C file automatically open and show the execution point when
>>> I halt execution and single step?
>>>
>> Yes.
>>
>> --
>> John W. Temples, III
>>
'[PIC]RE: p1.exe has stopped working'
2010\06\23@105429
by
'[PIC] p1.exe has stopped working'
2010\06\23@105835
by
And for Windows7 read this article found on my MSDN database:
msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx
{Original Message removed}
2010\06\23@113953
by
Bob Blick
On Wed, 23 Jun 2010 09:51:07 -0400, "David Novak" said:
> I found the issue... The path to my source code was too long. After
> reducing the path, the project builds without error and I'm able to
> debug at the source code level.
HiTech PICC also had that problem up until a few years ago.
Cheerful regards,
Bob
--
http://www.fastmail.fm - Access all of your messages and folders
wherever you are
2010\06\23@115458
by
Dwayne Reid
At 07:51 AM 6/23/2010, David Novak wrote:
>I found the issue... The path to my source code was too long. After
>reducing the path, the project builds without error and I'm able to
>debug at the source code level.
>
>David
Good catch.
I recall this being a problem with early versions of MPLAB and still,
to this day, always install MPLAB right off the root of my working
drive (D:) rather than where the install (setup) program wants to put it.
However, I don't recall this being a problem with the Hi Tech software.
Thanks for letting us know!
dwayne
--
Dwayne Reid <RemoveMEdwaynerTakeThisOuT
spamplanet.eon.net>
Trinity Electronics Systems Ltd Edmonton, AB, CANADA
(780) 489-3199 voice (780) 487-6397 fax
http://www.trinity-electronics.com
Custom Electronics Design and Manufacturing
'[PIC]RE: p1.exe has stopped working'
2010\06\23@115900
by
Jan-Erik Soderholm
OK.
That page also says :
"This problem was first corrected in Microsoft
Windows XP Service Pack 2."
Does anyone realy run something older then SP2 ?
The current Windows XP is SP3.
And that talkes about the PATH environment variable.
I thought the problem was with the actual directory path
to the source code, not the PATH variable...
Jan-Erik.
On 2010-06-23 16:54, @Home wrote:
> Hello Eric,
>
> In windows XP there was a limnitation:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;832978
>
> Regards
>
> Harry
>
> {Original Message removed}
'[PIC] p1.exe has stopped working'
2010\06\23@122235
by
Jan-Erik Soderholm
On 2010-06-23 17:54, Dwayne Reid wrote:
> At 07:51 AM 6/23/2010, David Novak wrote:
>> I found the issue... The path to my source code was too long. After
>> reducing the path, the project builds without error and I'm able to
>> debug at the source code level.
>>
>> David
>
> Good catch.
>
> I recall this being a problem with early versions of MPLAB...
It is still, as far as I know, a "problem" when building
projects in absolute mode. The tools used in relocatable mode
does not have this limitation.
Jan_Erik.
2010\06\23@123738
by
David Novak
|
My path was about 120 characters, including the entire file name. That,
combined with the PICC command line, must have put me over the limit.
I didn't find this documented anywhere, so I don't know what the limit is.
To fix it, I created an MS Windows junction point and used the junction
point within the build tools. This allows me to keep the source code
within a much larger project directory structure and in a location that
is backed up regularly.
David
On 6/23/2010 10:11 AM, Jan-Erik Soderholm wrote:
{Quote hidden}> How long is "too long" ?
> And is/was this documented ?
>
>
> On 2010-06-23 15:51, David Novak wrote:
>
>> I found the issue... The path to my source code was too long. After
>> reducing the path, the project builds without error and I'm able to
>> debug at the source code level.
>>
>> David
>>
>>
>> On 6/20/2010 5:55 PM, John Temples wrote:
>>
>>> On Sun, 20 Jun 2010, David Novak wrote:
>>>
>>>
>>>
>>>>> You need to import the .COF file for debugging (or given the age of
>>>>> the compiler, it might be a .COD file).
>>>>>
>>>>>
>>>> I did import the cof, but it acts the same as importing the hex.
>>>> Should the C file automatically open and show the execution point when
>>>> I halt execution and single step?
>>>>
>>>>
>>> Yes.
>>>
>>> --
>>> John W. Temples, III
>>>
>>>
2010\06\23@130515
by
To create a short path that always works, as i do with current projects, is
to create a network drive to that project.
Like NET USE P: //server1/projectdatabase/project
In this way the path name wil allways short = P:\
Harry
{Original Message removed}
More... (looser matching)
- Last day of these posts
- In 2010
, 2011 only
- Today
- New search...