#NOISE_2.SXP
19 messages in this thread
G. _ "Parity 1 check" Error_ ?????
I was using the setup regarding Animating SXP water in the Inside 3D Studio
Book starting on Page 794 with a few variations. I did not use a grid I
created a polyline circle in the shaper and brought it in to the 3D Editor then
applied the Blue Plastic material and substatuted the NOISE_2.SXP for the
original one. I also had a larger area and used a setting of end offset x,y,z
100, 100, 100 with a size of 100.
Could this be where I am having trouble.?
She locked up so tight it wouldn't even warm boot.
Any Suggestions??
Murph'
A parity check error is probably a memory parity error, James… It's got
nothing to do with the application software that you're running. It sounds like
it's time to run some diagnostics on your machine.
Good luck,
– G
G.
>> ….probably a memory parity error, James… It's got nothing to do with the
application software that you're running <<
I know ….. probably just wishful thinks on my part…I've been haveing
trouble with this machine and just thought I solved the local bus problem by
using an IAS SCSI controller to stop the appearant problems…looks like I'm
not through with this POS Yet!! <g>
I was also thinking that because this was a huge 9MB Autocad AME/DXF file I
brought in and used Optimize on plus the fact that the waters surface area
spans 17,518.83 units accross might have something to do with it.
Would Scalind everything Down Help on Memory Consumption? I wouldn't think
there's any difference to the Computer.
Murph'
Remember, when bringing in large AutoCAD files, always make sure that no
discreet entity has more than 64K faces.
– G
That's a good point Gary, How would I be able to determine that?
I would not be the one creating the files.
I need to be able to explain to a Draft Person How to properly constuct these
scenes so as to make sure there are never over 64K, this I know, What I don't
know is How to communicate that to him.
I don't even know how someone with AutoCAD would determine that since I don't
deal with that particular product and when I did we never did 3D.
Therefore when I'm speaking to an AutoCAD Person Not a 3D Studio Person and I
mention "Faces" it's usually all News to them.
Is there a "short Form" explaination that you could give me that would enable
me to precisley explain this to a none 3D Studio Person?
Thank's in advance.
Murph'
I'm sure that one of the many CAD jocks either here or in the ACAD forum can
help you with that answer — tho I'm not one of them. Not enough left-brain
grey-matter, perhaps.
– G
G.
>>> Not enough left-brain grey-matter, perhaps. <<<
Ya'…Sure….<BG>…and Hawian Shirts _decrease_ in Value over the years,
<GR&D>.
Murph'
I agree, it would be very difficult for a non-3DS ACAD-user to understand how
many "faces" a particular model would generate. It is varies considerably
upon what type of entity is being exported and for an ACAD-user, the rules
have changed considerably (a tiny 12 arc polyline could import as 1300 faces
for example).
For a start, have them organize the model according to layer – with an
emphasis on not having any one layer too complicated. Then if the model does
contain over 64k on an imported layer/object you can at least track down
which layer is too large (by name) and can have the ACAD model simplify it or
break it into more layers.
– Phil
p.s. Check out chapter 11 of Insisde 3D Studio as a reference <g>.
Hi Phillip!
>>> chapter 11 of Insisde 3D Studio as a reference <g>. <<<
I _+Knew+_ You were Gonna Say That! <BG>
Murph'
Gary's right about Parity Errors. There are very few possible causes of a
Parity Error:
1. Memory parity check circuitry detects a word in memory whose actual parity
and parity bit do not match. This means either bad memory, or bad parity
detection circuitry. In either case, the system executes a jump to a ROM
routine which displays the PARITY ERROR message and halts the CPU entirely,
requiring a hard reset or power cycle.
2. A really messed-up program blows up wildly, branching or jumping to some
random data and trying to execute it as if it were valid code, and the data
just happens to contain bytes that just happen to work out to a jump to the ROM
routine mentioned above, thus "faking" a Parity Error.
3. A prank program carried by a virus or Trojan Horse does the effect of #2
deliberately.
As you can see, none of them are good news. #1 is the most likely, with #3
a distant or close second or perhaps surpassing #1 depending on how thoroughly
you protect your site from viruses and the like. #2 is _astronomically_
unlikely. You should only consider it as even a remote possibility if you are
getting the error on two completely different machines, and you have had your
entire site thoroughly screened for viruses and the like by an expert who knows
how to find such things even if they're too recent for McAfee's and the like to
know about 'em.
Thanks!
I suspect that I'm still having trouble with this system in spite of the fact
I've replaced a VL Bus Controller with an regular ISA Bus Controller to solve
my other problems.
I'm Begining to Not Like Local Bus Motherboards.
Murph'
Partiy errors are most often memory bound, so it should have nothing to do with
what bus your MB is. It's the memory on the board that's probably giving you
this problem.
John Tissavary (LUNA cie, inc)
Yes John I agree as far as the Parity error goes….however I've been having
ongoing BusLogic and Diamond (read that unsupported out of business
motherboards inc.) Local Bus MotherBoard Problems that are related to either a
Bad BusLogic Local Bus Controller or a Bad MotherBoard….I've Just Returned
the BusLogic Controller for the Third Time and they swear the Board is Good!
Therefore I am now forced to purchase a New MotherBoard come to find out some
"wise-guy" named Mr. Lao Bought these all up at $100. a pop and re-feed them in
to the market….Guess Who got One…Bingo!
By the Way for those of you with unsupported Diamond Mother Boards I'm Selling
the Phone Number to Mr. Lao's Personal Residence.
Do I hear $5. <GR&D>
As you can see I've spent a considerable amount of Detective work on these
problems. <g>
Murph'
I always went with AMI motherboards. Expensive but super reliable and super
fast. I've never heard of anybody who had troubles with AMI, FWIW – you may
want to check them out instead of going with cheapo mfg's
John Tissavary (LUNA cie, inc)
John,
>>> cheapo mfg's <<<<
Arent' they a division of WonHungLow? 🙂
Murph'
>> >>> cheapo mfg's <<<<
>> Arent' they a division of WonHungLow? 🙂
I gather you were joking but in Portland, OroGone,
there is a resteraunt in the dwindling China Town named
Hung Far Low
In Burbank, until just recently there was "Chow's Kosherama". And in
Little Tokyo, LA, there is (or at least was) a little curry resturant that had
a sign on the door with the hours of business listed, and the bottom read
(spelled exactly this way, I swear) "Crosed on horidays".
David
David,
>>> "Crosed on horidays". <<<
I highly suspect that was some intentional self effacing humour.
Murph'
Hi Albert.
>>> in the _dwindling_ China Town named
Hung Far Low <<<
How is it possible that China Town is _Dwindling_??
It's got to be the only place in the country that has a _dwindling_ Asian
Population. Allthough that might be where some of our recent Asian Freinds are
coming from as I've noticed the population increasing in the Northern States.
It's hard to gain their confidence and respect. Although I can't say I've had
much dealings with the Asian population since I've been back in-country, I
certainly enjoyed my 18 months stay in the Korean Peninsula. I'm Serious. I
didn't hang out in the usual GI Area's.
I was probably one of the few GI's ever allowed to, much less get invited to,
many of their civilian functions. You see… in Asia…._we're_ the
outsiders…kinda gives Ya' a perspective on how they feel in this country!
<BG>
I always regret loosing touch with some of my Korean Freinds…I'd even sent
letters to the Army as well as Korean Civilian consulates trying to find some
of them after I'd left service, my big problem was, I'd been sending letters
with the Korean Address Photocopied on the outside of the envelope and when I
lost the address I was out of luck because the Army and Korean (KATUSA)
organizations won't give out that kind of information based on former duty
stations….we were assigned to the Army Security Agency ….So it's completly
out of the question. Too Bad Cause' I really had some very good freinds there.
Before I start going down memory lane here, I better cut this off because I see
we are in the IPAS Usage Area….
Before you ask, Yes I'm a dealer and Yes I'll be selling the Xaos, Pennelo
Routine which will be shipping in October.
I'm Taking Orders now if your interested.
Murph'