--
Thanks
Ray L. Nicoli
remove "SPAMBLOCK" from e-mail to reply
Sent via Deja.com
http://www.deja.com/
SW2000 sp10
Win 2000
3dLabs VX1
--
Leonard Hursh
Escofab Inc.
"Ray L. Nicoli" <rni...@SPAMBLOCKiddaerospacecorp.com> wrote in message
news:3a534...@news.foxinternet.com...
Good luck!
trivia note - this problem will even occur if the interfering part is
hidden. The interfering part needs to be corrected or suppressed to prevent
the line-drop problem.
good luck
-ed
"Ray L. Nicoli" <rni...@SPAMBLOCKiddaerospacecorp.com> wrote in message
news:3a534...@news.foxinternet.com...
In article <h9b56.54982$Y6.12...@news1.mntp1.il.home.com>,
Ray L. Nicoli <rni...@SPAMBLOCKiddaerospacecorp.com> wrote in message
news:3a534...@news.foxinternet.com...
What does Crtl+Q do?
I often have this problem, and I'm very Frustrated by it.
This probably is not your problem but I'll mention it anyway. Make
sure that your line color is not the same as the background color. If
it is then go to:
>options
>view system defaults
>wireframe/hlr
>edit
"choose a non background color"
ok
I replicated half your problem. I got the line to dissapear but when I
printed the drw it all printed out ok.
good luck
tony
In article <3a534...@news.foxinternet.com>,
Please, If you can reproduce this problem, is it a BUG?
Thank You
In article <93idbq$b7h$1...@nnrp1.deja.com>,
I can't reproduce it. I get exactly what I would expect. I tried it by
putting the hole in the block first, and also as an assembly feature.The two
blocks are mated on one of the 3x3 surfaces. The hole goes through the
center of the 3x3 faces on one block. The section line is parallel to a 1x3
surface, through the center of the hole.
Jerry Steiger
In article <3a534...@news.foxinternet.com>,
"Ray L. Nicoli" <rni...@SPAMBLOCKiddaerospacecorp.com> wrote:
NT 4.0 SP5
SW2000 SP10
Dell Precision 410
PII 750Mhz
1Gb Ram
GVX 420 Video
8GB SCSI drive
Don Jackson
My problem demonstrated by SolidWorks Instant Website...
http://www.3diw.com/login.asp?u=f40d32cf6&f=Assem15469
password: guest
Any suggestions would be helpful.
Thanks
Jake,
That's exactly what I expected to see from your description, and I finally
found a way to get something like it. After making the drawing, I changed
which part had the hole in it. Now the drawing is confused and looks like
yours. Regenerating the assembly doesn't fix the drawing.
Could that be how your drawing got messed up?
Jerry Steiger
My example is quite simple compared to the drawings I create in SW2000.
These drawings will contain from 20 to over 100 components.
I will export them into ACAD to "FIX" them up. Before I send them out
for production because the lines that are missing will not print or
export into DXF or DWG.
I'm using:
PII 450 mhz
384MB RAM
WinNT 4.0 SP5
SW2000 sp10
Accell Graphics Accell Star 8 II (8megs)
Thanks for your input
Jake
Anyone else...?
Regards:
Janos
unfortunately we have trouble with Solidworks 2000 and 2001.
SolidWorks abends when I try to load drawings from a network drive and
then I get a "blue screen". Loading drawings from local drive C: works
fine.
The network seems to be fine and there are no problems with other
applications (ME10, SolidDesigner, AutoCAD, MS-Office...). We can copy
large files without any error from and to the network.
What could be wrong?
DELL Dimension 4100 PIII 866 MHz, 128 MB RAM NVIDIA 4xAGP
Novell NetWare 5.1 SP2a, NetWare Client 3.21 P1 (German)
Has anyone encountered this and is there an easy fix? Thanks in
advance.
Peter Duennebeil
Regards:
Janos
Now that you mention it, your crashing could be caused by network problems.,
SWX requires a pristine connection if you are loading and saving your work
over the network. SWX is constantly querying open files. A corrupted or
dropped packet can cause the program to lock up, behave strangely, or error
out (Dr W.). I found this to be the problem with a couple of machines we
have that were connected to the same hub. The symptoms were very much like
the ones you describe. It took alot of trial and error to isolate this
phenomenon.
A quick way to check is to open the assembly, do a "file, find referances,
copy" and copy all of the files locally. Just drag and drop copying from
explorer won't work because all of the network paths are imbeded in the
assemblies. Using this method strips all of the files of external (external
to the folder in which they were copied) referances. Work on the assembly
from this local folder and see if it does the same thing.
We'll be getting Win2000 Server pretty soon. It's supposed to have some
built in utillities that help track these spooky problems
Regards
Mark
Janos wrote in message <3AA3F29A...@oznet.net.au>...
msm wrote:
>
> Janos,
>
> Now that you mention it, your crashing could be caused by network problems.,
> SWX requires a pristine connection if you are loading and saving your work
> over the network.
We are working on a network, but not from a network. Ie. I am backing up to
the network drive and have access to some other resources on it but that's
all. We strictly work from the local drive. This is what I am suggesting to
other guys working on AutoCAd as well but they tend not to listen and they
have a continuous struggle with all sorts of problems.
>SWX is constantly querying open files. A corrupted or
> dropped packet can cause the program to lock up, behave strangely, or error
> out (Dr W.). I found this to be the problem with a couple of machines we
> have that were connected to the same hub. The symptoms were very much like
> the ones you describe. It took alot of trial and error to isolate this
> phenomenon.
The problem we were stuggling with was that SolidWorks itself crashed (and
then did not even start) because of this user profile problem. As it
happened and also before it we worked as described in the previous
paragraph, strictly from the local drive.
>
> A quick way to check is to open the assembly, do a "file, find referances,
> copy" and copy all of the files locally. Just drag and drop copying from
> explorer won't work because all of the network paths are imbeded in the
> assemblies. Using this method strips all of the files of external (external
> to the folder in which they were copied) referances. Work on the assembly
> from this local folder and see if it does the same thing.
We are working on big assemblies (220+ MB). For backup we ZIP the project
(size down to 35-75 MB) and only the zipped project is backed up on the
network drive and afterwards on CD's.
>
> We'll be getting Win2000 Server pretty soon. It's supposed to have some
> built in utillities that help track these spooky problems
I am a bit afraidd of using W2k as yet - probably in a year tie or so I
will make an attempt.
Thanks for your feedback.
Regards:
Janos