Jump to content
RockWare Support Forum


  • Posts

  • Joined

  • Last visited

Everything posted by JimReed

  1. Do you have at least three points for each stratigraphic unit? Unlike lithologic modeling, the stratigrahic grid interpolation requires at least three points to estimate a surface.
  2. Hi Derek, The following comments refer to numbered items within the attached image. 1. The Graphics / Images / Google Earth / Vertical - Two Points Advanced program will position images as vertical panels within Google Earth. 2. To use this program, you'll need to create a datasheet with the coordinates for the lower-left and upper-right corners of each image. 3. Specify which column contains the relevant data. Note the Vertical Position tab. This allows you to vertically exaggerate and vertically offset the panels. 4. The panels will be displayed in Google Earth. If you get stuck, please send an email to jim@rockware.com. Best regards, Jim Reed.
  3. Yes, if you can convert each resistivity profile to an image (e.g., PNG file). You'll need the XYZ coordinates represented by the lower-left and upper-right corners of the profile. Here's a link to the documentation: Displaying Multiple Images as 3D Vertical Panels (rockware.com) and here's an old video (RockWorks15) that describes the process (below). The screenshot at to base of this message shows where to find the program. Also; there are several sample/tutorial files. Another method is to export your resistivity data as XYZG points, create a block model, and slice/dice the model to create a 3D fence diagram, but that's a lot more work. If you get stuck, send me an email: jim@rockware.com - Jim Reed. Importing the actual resistivity data, creating a block model, and slicing/dicing is a lot more work.
  4. Hi, Right click on a column title (item #1) and a dialog box will appear (item #2). Select "X or Y Coordinate" (item #3) for the X column and then choose the coordinate system (item #4) that you're using for the resistivity points. Do the same for the Y column. For the Z coordinates, select the "Linear (Z) Dimensions" option (item #5) and the menu will change to show the linear units (e.g. Feet, Meters). Select the appropriate z-units. Now, the datasheet columns should show the units and you're ready to go. These coordinate designations will allow you to have data tables that are not in the same units as your project dimensions (item #6). For example, let's say that you've set your Project Dimensions up in UTM meters but your resistivity data is in State Plane footage coordinates. The program will automatically convert your resistivity coordinates to project coordinates (item #6). This is a big deal for clients who have different data sets in different units. It becomes especially useful when exporting to Google Earth, in which the program will automatically convert everything to longitude/latitude/meters (the only units that Google Earth imports via KMZ files). There's a video button (item #7) that will display a popup menu with four video links. Select the one labeled "Changing Datasheet Names & Column Types". This will launch a 2-minute video that describes all of this in more detail. You can also press the F1 key from within the datasheet editor and navigate to the datasheet documentation for non-video, textual instructions: file:///C:/ProgramData/RockWare/RockWorks17/WebHelp/introduction.htm Also, if you click on the Help button within the Column Parameters dialog you'll see that there are other things that you can do with the column types (e.g. density conversions, hyperlinks, etc.) Good luck and best regards, Jim Reed.
  5. Sorry ... documentation error. Please select the tab labeled "Other". - Jim Reed.
  6. Hi Craig, The volumetrics for a stratigraphic diagram based on grids are computed by; (1) subtracting the subface (base) elevation from the corresponding superface (top) elevation, (2) multiplying by the result by the cell x-size and y-size (i.e. base * width * height = volume within that "column"), and (3) summing the results for all columns. Conversely, the volumetrics for a block model are computed by summing the volumes for all voxels that meet some criteria (e.g. all voxels with a node value > 3.2 and <3.9). Now, let's say that we create a voxel model based on grid surfaces (this is what the Stratigraphic Model / Save Numeric Model option does). The program will assign the voxel values based on the bounding grids that lie above and below the voxel midpoint. Given that a voxel midpoint may be just below the corresponding, overlying grid node, 49% of the voxel space could actually be above the superface grid node. The same applies to voxel midpoints that are just above the corresponding underlying grid node - 49% of the voxel could actually be below the subface grid node. This is why the volumetrics for a block model will never match the volumetrics for a grid-based model. As you reduce the z-spacing for a block model the volumetrics will start to converge, but they'll never be exactly equal and the model generation will take longer. The trick is to establish a z-spacing in for which the differences between the volumetrics is acceptable. If the voxel-based profiles don't look right, then I suspect that the z-spacing is too large. Best regards, Jim Reed.
  7. Hi Edward, Doh! I was assuming that you were originally talking about a straight hole (think mining). Someday I'll learn to read more carefully. Anyway, this is not a widget thing (although I still intend to add the program that I outlined). Instead, I'm thinking that this particular program merits a more serious program that we'd add to the Utilities / Survey menu. Input: - Downhole survey (planned or actual) file. - Type of target object: - Point: X,Y,Z - Line: X1,Y1,Z1 - Plane (Fault): X,Y,Z,Dip Direction, Dip Angle Output - For each point within the well (say 1-foot increments); - XYZ for well - Bearing to closest intercept with object - Distance to closest intercept with object - XYZ for object intercept Sound right? Alison essentially covered the borehole manager solution that I was alluding to (i.e. doing it graphically). Best regards, Jim.
  8. Hi Edward, As you've discovered there are no widgets to solve this problem. In theory, you could do it within the Borehole Manager, but that's a lot of hassle. Instead, I propose that we create a new widget along these lines: Input: - Collar X - Collar Y - Collar Z - Borehole Dip Direction - Borehole Dip Angle - Fault X (any point along fault) - Fault Y - Fault Z - Fault Dip Direction - Fault Dip Angle Output: - Intersection X - Intersection Y - Intersection Z - Distance From Collar To Intersection - Vertical Distance From Collar To Intersection (Phrased such that it accommodates drilling upwards for underground applications). If this sound right, we'll add it to RockWorks17 and get you an early beta/trialware release as soon as possible (say two or three weeks). If that doesn't work for you and you've only got one hole, just send me the input data and I'll send you the answer. Best regards, Jim Reed.
  9. Thanks for the clarification and image - that helps a lot! We use the horizontal "lithoblending" for modeling these types of non-contigiuous units (e.g. transgressions/regressions). I'll attach some sample images. The catch is that the modeling is much slower than the stratigraphic or geochemical/geophysical modeling. There are also some tricks for adding regional dip and structures. For more information, search the help messages for "Lithologic Modeling".
  10. Hi Matteo, Like Mitch, I am also new to the term "eteropic" but I'm guessing that you're referring to showing vertical facies changes. If the change is based on a single parameter (e.g. clay content), you can make a pseudo-continuous block/solid model of that parameter (stored as I-Data or P-Data) and truncate it (i.e. set the node values above and below the superface/subface) based on non-eteropic surfaces (see attached Figure 1). When you plot 3D models and create 2D cross-sections, you're essentially showing portions of two different models - a stratigraphic model (for the vertically homogeneous units) and a block model for the anisotropic parameter. Admittedly, this is not an exercise for beginners. Please let me know if this is what you had in mind, and if so, I'll create a step-by-step video and post it to YouTube. Best regards, Jim Reed.
  11. If you encounter a cryptic error with the AVI output from a RockPlot3D Animation such as the following .. - Windows Media Player: "Windows Media Player encountered a problem while playing this file." - QuickTime Player: "Error: -50: an unknown error occurred (540 degree rotation.avi)" - Windows Live Photo Gallery: "Photo Gallery can't open this photo or video.  The file may be unsupported, damaged or corrupted." - Windows Live Movie Maker:  No error – plays video but it's entirely black. ... the problem may be in the "CODEC". The "CODEC" (COmpressor/DECompressor) determines how the video will be compressed. The 64-bit version of Windows-7 appears to have inconsistent and unpredictable incompatibilities with some CODECs that manifest themselves as problematic AVIs. The solution, is to use a different CODEC other that the default. This is accomplished by clicking on the pull-down menu that appears when creating an animation within RockPlot3D. Specifically; A menu titled "Video Compression" just before the AVI file is saved. - Click on the pull-down button next to the item labeled "Compressor:". - Select a different compressor (e.g. "Microsoft Video 1"). - Change the "Compression Quality" to 100. If this doesn't work, you may need to experiment with other CODECs.
  12. Below is a a list of files that have been temporarily uploaded to our FTP site. Please let me know when you're done downloading them. My plan is to remove them once you're done. Otherwise, our server will start to crawl if others are using this site instead of YouTube. Google (YouTube) has more server horsepower that we do. Best regards, Jim Reed. http://www.rockware.com/support/files/Permanent/Videos/ancient_rome_fly-over.mp4 http://www.rockware.com/support/files/Permanent/Videos/concept_2d_vs_3d_modeling.mp4 http://www.rockware.com/support/files/Permanent/Videos/concept_multivariate_modeling.mp4 http://www.rockware.com/support/files/Permanent/Videos/concept_volumetrics.mp4 http://www.rockware.com/support/files/Permanent/Videos/hd_configuration.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_backup_and_restore_rockworks_database.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_convert_gamma_to_uranium_grade.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_depth-register_raster_logs_and_other_images.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_drape_image_over_surface.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_import_excel_data_into_utilities_datasheet.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_launch_rockworks.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_plot_oil_leases_in_google_earth.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_rectify_and_crop_images_to_project_dimensions.mp4 http://www.rockware.com/support/files/Permanent/Videos/how_to_use_project_manager.mp4 http://www.rockware.com/support/files/Permanent/Videos/humor_billy_saves_the_day.mp4 http://www.rockware.com/support/files/Permanent/Videos/idaho_springs_fly-over.mp4 http://www.rockware.com/support/files/Permanent/Videos/part_4.1_utilities_overview_introduction.mp4 http://www.rockware.com/support/files/Permanent/Videos/part_4.3_utilities_overview_grid_options.mp4 http://www.rockware.com/support/files/Permanent/Videos/plot_borehole_locations_in_goggle_earth.mp4 http://www.rockware.com/support/files/Permanent/Videos/plume_modeling_02.mp4 http://www.rockware.com/support/files/Permanent/Videos/project_fly-overs.mp4 http://www.rockware.com/support/files/Permanent/Videos/request_for_video_ideas_01.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockware_consulting_42_second_commercial.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_accidental_art.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_case_study_denver_center_plume_part_3_of_3.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_case_study_denver_federal_center_plume_part_1_of_3.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_case_study_denver_federal_center_plume_part_2_of_3.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_coal_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_cone_penetration_testing_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_contaminant_plume_modeling_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_dam_sites_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_displaying_images_in_3-d.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_education_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_geotechnical_soil_investigations_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_geothermal_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_groundwater_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_hydrocarbon_exploration_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_hydrochemistry_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_industrial_minerals_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_intro_main_screen_tour.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_intro_part_1_general_capabilities.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_intro_part_2_application_examples.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_intro_part_4.2_utilities_overview_map_options.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_landfills_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_mining_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_oil_and_gas_production_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_tunneling_intro.mp4 http://www.rockware.com/support/files/Permanent/Videos/rockworks_uranium_intro.mp4
  13. If Mitch's solution (the workaround link) doesn't work, I'll create an FTP site where you can manually download the videos. Please let me know and I'll start setting it up. - Jim Reed.
  14. Does the ban apply to just RockWare videos or does it apply to all Youtube videos?
  15. For more information about RockWorks versions, please select the following link ... RockWorks Revisions List To download the latest version of RockWorks14, please select the following link ... Download Latest Version of RockWorks14
  16. For more information about RockWorks versions, please select the following link ... RockWorks Revisions List To download the latest version of RockWorks14, please select the following link ... Download Latest Version of RockWorks14
  17. Dear “JWripple”; (1) What sets RockWorks aside from other programs? In my biased opinion (I work at RockWare), there are multiple factors that have determined the popularity and applicability of RockWorks within Civil Engineering. Each of the following twelve items is fundamental. Without any one of them, RockWorks just wouldn't be RockWorks. Relational Database: We tried for years to work with non-relational (aka "flat") datasets. Once we switched to a relational database, things got much better. It certainly didn't hurt that we chose to use the Microsoft Jet Engine. This allowed people to access our database from Access and opened up a world of possibilities, including; shared data on network servers, data transfer with in-house databases, and user-extensibility (adding your own tables to the RockWorks database). Had we chosen to use a proprietary database, things would be a lot different (e.g. I'd probably be unemployed.) 2D Graphics: As tempting as it is to exclusively focus on the sexiness of 3D graphics, the geo-engineering market is entrenched in 2D, CAD-style graphics for good reason. These are the "meat and potatoes" diagrams that engineers use on a daily basis. We've tried to give the 2D equal priority to the 3D and it's paid off. Geo-engineers can survive on 2D alone whereas a 3D-only package just doesn’t cut it. 3D Graphics: Civil Engineers wear two hats. The aforementioned 2D graphics is what they use for getting the job done while the 3D graphics is what they typically use to convey their concepts to clients and non-engineer types. This is the "eye candy". On the other hand, even engineers can benefit from the spatial understanding that 3D graphics can provide for complex geological environments. As you’ve probably noticed by now, our 3D stuff is starting to scratch the “soft underbellies” of some very high-end products costing orders (yes orders) of magnitude more. What’s more, we’ve made our 3D display engine (RockPlot/3D) a free standalone so that you can send your diagrams to clients, along with the 3D engine so that they can manipulate it (e.g. rotate, enlarge, enable/disable layers, etc.) rather than watching a static slide show. Hey, it worked for Adobe with their free Postscript viewer, and it’s working for us too. Modeling/Interpretation: Just showing the data in 2D and 3D isn't enough. Most projects require some sort of interpolation to fill in the missing information between the boreholes. The two-dimensional, grid-style modeling isn't enough either. Geotechnical properties vary in all three dimensions (actually four dimensions when you consider time). We originally limited our modeling to grids (surfaces), assuming that true 3D modeling was the domain of the "big guys". Thanks to the folks at Intel, we started making 3D block models and that led us into volumetrics, the "end game" for many civil applications. Most importantly, we chose not to go down the path of proprietary, black-box, secret modeling algorithms that don’t stand up in court. Relative Ease-of-Use: Note the term "relative". Civil Engineering is complicated stuff. We spend most of our time trying to make the program easier and more intuitive. Unfortunately, the enemy of ease-of-use is flexibility. It's a constant tug of war. I once had a guy ask me for a new feature while also telling us that the program was cluttered with too many features (all in the same sentence!). The best thing that we ever did to address the complexity issue was to switch to the expanding/collapsing tree-style menus that implicitly organize topics while simultaneous hiding non-applicable options. By integrating an extensive context-sensitive help system in these menus, we’ve add more distance between us and our competitors. Documentation: Engineering applications have historically treated documentation as an afterthought. We’ve done the opposite. Our technical writers are integral to the design process. Writing up tutorials and case studies always results in changes to the program. Along the same lines, our consulting services have given us a competitive edge for two reasons; (1) Our consulting staff are the same people who provide technical support. This means that when folks call for answers, they’re talking with experience users as opposed to a call center where drones are reading from scripted decision trees. (2) Our technical writers, project consultants, testers, and technical-support people sit within shouting/striking distance from our programmers. As a consequence, when somebody’s trying to get a project done and they encounter a problem, the programmers are compelled by self-preservation (fear, shame, ridicule, etc.) to quickly address the problem Affordability: We started out in 1983 at $49 in a market where the closest competitor was priced at $40k. This was a good move. We certainly weren't making as much money on a per-unit basis as the competitors, but we were saturating the market. This in turn allowed us to gain far more feedback from a much larger clientbase. The result is a product that has been essentially designed by thousands of geologists and engineers rather than a handful of "sugar daddy" clients. As a consequence, RockWorks is the most flexible and multi-faceted product in the market while still being relatively usable (there's that "relative" term again). Don't get me wrong: There are better products for specific elements within RockWorks, but nobody pulls it together into a single, affordable product like we do. In fact, many of our civil engineering clients use RockWorks for the day-to-day work and other, more-specialized, competing products for occasional projects. Peaceful coexistence. The other benefit to the lower price-point is that everybody within an organization can use it. This in turn, means that synergies form when co-workers are cross-training each other. Compare this to the designated "high-priest" approach whereby a single person (aka “geek”) within an organization is specially trained to use a high-end monster. This type of organization has gone the way of the personal secretary. Easy word processing eliminated the need for professional typists. Open Attitude: As mentioned above, we don't use a proprietary database, proprietary algorithms, or for that matter, proprietary anything. This eliminates the risk in using RockWorks because you can always move the data out of the program and into something else. It’s not such a big deal in Civil Engineering, but we seen some horror shows, especially in mining, where you can get “locked” into a program that never lets your data out in the event that you need to switch to something else. We’ve also seen products that have secret algorithms that require you to subpoena the programmers (no kidding) for expert testimony in the event of litigation. Dynamic Distribution: As you've probably noticed from our constant revisions (see http://www.rockware.com/rockworks/revisions/index.html), this is a very dynamic product. We add, on average, about one new feature every day and make these available every two weeks at no charge. Admittedly, we add new bugs along with the new features, but consider the alternative attitude of "We'll have that fixed in the next version that you can buy in about a year or two." This responsiveness to suggestions and complaints is something that we're very proud of. I sometimes joke that it's like R&D without the "R", thanks to a vocal userbase. For example, we're currently working on time-based data (e.g. sampling monitor wells for various contaminants over time). We'll be trickling out new time-based applications for the next two months at no charge to existing customers. Integration: As we add more features, we're able to "leverage" existing features into new applications. For example, we started out with individual stereonet diagrams. Then we added downhole fractures to the database. It only made sense to pass the fractures to the stereonet subroutine and create maps of stereonets. As the program grows the possibilities for "hybrid" applications become exponential. Trialware: The decision to make the program available on a try-before-you buy basis was something that was admittedly scary at first but it sure worked. In one simple step, we eliminated the stigma associated with the lower price. People started comparing it side-by-side with higher priced competitors and we came out ahead. In addition, people started to notice that many of our competitors don’t offer free trial version relying instead on return policies that require a call to your lawyer. Generic Applications: A longstanding blessing/curse for RockWare has involved our desire to serve multiple markets. Specifically, we target the petroleum, mining, civil engineering, environmental, hydrological, and academic markets. At times this is frustrating because we give priority to generic applications as opposed to more esoteric, industry-specific utilities. On the other hand, it’s also proven to be a great way to offer applications that are more flexible that what you’ll see in industry-specific products. More importantly, many applications that were introduced to appease one market turned out to be equally applicable within markets that we never considered. For example, we added trend-surface analysis for the petroleum people but it turned out to be a hit within the hydrology market for modeling potentiometric surfaces. The best example for Civil Engineering involves the solid modeling. We were focused exclusively on mining when it first came out. But then, we were amazed by how many people were using it for modeling geotechnical properties such as compaction, cohesion, swelling, etc. It’s technology transfer. Lately, we’ve been amazed by how many people are using the deviated borehole capability (originally designed for the oil and gas industry) to model tunnels. That’s why we recently added the capability to compute the volumetrics of materials inside a borehole (aka tunnel). Another benefit of the generic/multiple-market approach is that we’re able to sell far more units thereby holding the price down to something that everybody can afford. I originally considered answering your question with a feature matrix, but opted to address the “big 12” instead. Now, onto your next question … (2) What benefits would making all these 2D and 3D models, sections, maps, etc. benefit others? First off, let’s consider you as “others”. The 2D and 3D diagrams should always be used as a quality check for your data. If a borehole is being plotted in outer space relative to the rest of the boreholes then there’s a good chance that the coordinates are wrong. If a model looks funky, it’s time to check the data as well as the modeling. In regards to others, that depends on who the others are. For example, diagrams and volumetrics (based on models) are typically required by contractors in order to provide cost estimates and implementation plans for site preparation and/or remediation. If you’re presenting to upper management or non-technical audiences (e.g. a town hall meeting), the rotating 3D models can be used to convey concepts that would otherwise to explain with words and arm waving. (3) How long would these models be valid and is that a relevant question in my case or is it based on the engineer who analyzes my work? We have some beautiful lithologic fence diagrams on the wall of our conference room that were hand-drawn as part of a USGS report from 1953. They’re still valid because the quality of the data and the reasonableness of the interpretations (conceptual models) are still valid. Good work is timeless. On the other hand, we’re often alarmed by the blind faith that some users place behind computer-based modeling. Don’t get me wrong, we’re proud of the modeling techniques, but … they’re very simple-minded and frankly quite dangerous if you fail to compare the models against the raw data. Critical thought has never been more important. I once heard a lady in the Ozarks say “Well, it must have been true because it was typewrit. [sic]” I feel the same concern about the computer modeling algorithms. For example, if you’re modeling elevations within an urban environment, you dang well better use the triangulation algorithm. On the other hand, if you’re modeling blowcount data, triangulation is totally inappropriate whereas the inverse-distance/anisotropic solid-modeling is the way to go. These types of considerations will determine if you’re models will stand the test of scrutiny and time. Best regards, Jim Reed
  18. For more information about RockWorks versions, please select the following link ... RockWorks Revisions List To download the latest version of RockWorks14, please select the following link ... Download Latest Version of RockWorks14
  19. For more information about RockWorks versions, please select the following link ... RockWorks Revisions List To download the latest version of RockWorks14, please select the following link ... Download Latest Version of RockWorks14
  20. For more information about RockWorks versions, please select the following link ... RockWorks Revisions List To download the latest version of RockWorks14, please select the following link ... Download Latest Version of RockWorks14
  21. Hi Ayman, Sorry ... we can't plot patterns within the 3D models, just colors. You can, however, plot profiles and sections using black and white patterns. Unfortunately, if you change all of your lithology patterns to black lines on a white background to accomodate black and white profiles and sections, the 3D models will appear as white blocks since we use the background color within the 3D diagrams. The attached "lith_bw_01.png" files shows a black and white lithology profile. In the meantime, I'll add 3D pattern plotting to our "wish list". Best regards, Jim Reed.
  22. Hi Will, The RockPlot-2D / Utilities / Legend program will "remember" the settings such that you can essentially append a standardized legend block to every section. It's a bit painful to configure the first time but once it's done, it can be quickly reused for subsequent diagrams. The attached file (legend_ideas_01.png) provides an example. Another (and probably better) idea is to use the ReportWorks utility. You can create a detailed page template with legends, logos, revision blocks, and then insert your diagram into the template. Best regards, Jim Reed.
  23. Please click on the RockWorks / Help / Online-Information / Revisions List option for more information.
  24. Is it safe to assume that this old thread has been addressed by the legend drawing utilities within RockPlot/2D? If not, we'll revisit the issue until it's "right" ...
  25. For more information, please click the following link ... http://www.rockware.com/rockworks/revisions/index.html
  • Create New...