From shott at snf.stanford.edu Sat Feb 8 10:04:37 2003 From: shott at snf.stanford.edu (John Shott) Date: Sat, 08 Feb 2003 10:04:37 -0800 Subject: Coral finally returns!!! Message-ID: <3E4546B5.74F672AD@snf.stanford.edu> SNF Lab Members: After a painfully long outage, Coral and the file systems are back on-line and normal lab operations can resume. Because we had to completely re-load and re-build things from the ground up, you may notice some other applications that are either missing or misbehaving. If you notice any problems, please report them to coral at snf.stanford.edu. Following is a bit of a discussion of what went wrong, what we learned, and how we hope to avert similar outages in the future. If you don't really care about that and are simply happy that Coral is operational, you shouldn't feel compelled to read the remaining material. So, if you are eager to get back to work, Team Coral apologizes profusely for the lengthy outage and will strive to avoid similar problems in the future. Thank you for your patience and your continued support ... John and Team Coral Following is a somewhat more detailed discussion of the Coral Outage of '03 ... Last weekend, we suffered what turned out to be a failure of the root partition and boot disk of the Sunray server. As we had recent and complete tape backups of everything on this disk we initially felt that we would be able to put in a replacement disk, reload it with data from tape, and be back in business. As you well know ... it didn't turn out to be a quick process. It actually took us and Sun field service a while to figure out that it was a disk failure. Why? Sunray has "Fiber Channel" disks that connect the disks to the rest of the system through a high-bandwidth fiber link as opposed to the more conventional electrical connection onto the main bus. Error messages were all related to fiber channel failures ... and time was wasted changing fiber channel components before it was finally determined that the real problem was the boot disk connected to the end of the fiber channel. Once we had the new disk in place ... it still took a long time to bring back the system. Why? This is largely due to some additional details and idiocyncracies of Fiber Channel disks that not only were we unaware of, but were also overlooked by Sun support and field service personnel until our problem got elevated to the "Field Service Superstars". Basically, more time was consumed because not everything as properly configured ... and steps that we took to recover that we were assured by various hardware/software field service personnel "should work" simply didn't. Finally, this outage didn't drag on because of lack of effort: Bill and Mike were working on this virtually around the clock much of the week. So, how will we reduce the likelihood of similar problems in the future? While we are still working out the details and the implementation of a comprehensive plan to eliminate future lengthy outages and to have greater fault tolerance, we do have some of the first steps of a plan in place: 1. Sunray has been given a second boot disk that will, hopefully, allow us to quickly recover and run from the second boot disk while were were resolving issues on the first disk. We will plan to add similar capabilities on other critical systems. 2. Critical file systems (your home directories, the coral database, etc.) will be moved to a RAID (Redundant Arrays of Inexpensive Disks, I think ...) disk system. Not only does this better protect the file systems themselves from hardware failure, but it will allow us to more quickly replace a failed server with a replacement server. 3. Get "backup Coral servers" in place where possible. We actually have some hardware intended for this purpose ... they are the Coral development machines. Unfortuately, we were not able to use them in this case because these newer machines run on a newer operating sysem (Solaris 8 vs 2.6), a newer database (Oracle 9i vs. 8), and the development version of Coral is not quite "ready for prime time". This combination of factors made it difficult to move "Production Coral" to the development hardware. However, once we complete the transition between the old OS and database to the new one, we will also be in a position to use the development server hardware as "emergency backup" Coral servers by connecting it to the "production database" that will be on the RAID disks. In other words, we will hope to make our development environment "look like" our production environment in terms of OS and database, so that we can use it as a backup to our production servers. So, let me once again apologize for the length of this recent Coral outage. We are working hard to learn from these experiences and to take steps to both increase our ability to withstand similar hardware failures and to quickly switch to backup hardware while we resolve problems with the primary hardware. Thank you for your continued support, John and Team Coral From shott at snf.stanford.edu Mon Feb 10 06:49:17 2003 From: shott at snf.stanford.edu (John Shott) Date: Mon, 10 Feb 2003 06:49:17 -0800 Subject: E-mail alert: watch for spam/viruses from legitimate SNF users. Message-ID: <3E47BBED.C95D191@snf.stanford.edu> SNF Lab Members: Please exercise extreme caution when opening e-mail from legitimate SNF lab members and mailing lists. We seem to have been the victim of some sort of spam/virus attach in which bogus messages appear to have been sent by legitimate SNF lab members and mailing lists. As of yet, we don't know the cause or whether these are merely nuisance spam or contain viruses, but please exercise extra caution before opening e-mail even it you think you know the sender. We'll keep you posted if/when we learn more ... Thanks, John From mahnaz at snf.stanford.edu Fri Feb 14 15:48:12 2003 From: mahnaz at snf.stanford.edu (Mahnaz) Date: Fri, 14 Feb 2003 15:48:12 -0800 Subject: Litho up date Message-ID: <3E4D803C.8D17181A@snf.stanford.edu> Hello all, I am very pleased to announce that the Karl Suss1 is up and running. I have ran quiet few tests and I was able to resolve 1 um line and space with vacuum recipe with minimal effort ( Post Exposure is a must). The new chuck has been modified and now there is a drawer between two Karl suss that extra chucks ad mask holders should be kept there. Please note that there are no reason to touch the power supply on the KS1 as the power supply for now only has the 365 nm and the intensity of the lamp is 15 mv/cm2. The DUV is not installed and the lamp housing is not here yet. You are responsible to report any issues and problems with the system and yellow light it even if the system has been yellow lighted for other problems. Your name all should have been transferred to the KS1 if you are qualified on KS2 if you can not enable the KS1 send a gentle and kind email to John Shott. Please take a good care of all the systems in the lab as I like to believe all of you have good intention. Have a happy Valentine's Day and a holiday From rcrane at snf.stanford.edu Tue Feb 18 11:57:47 2003 From: rcrane at snf.stanford.edu (Dick Crane) Date: Tue, 18 Feb 2003 11:57:47 -0800 Subject: Thank you Colby Bellew Message-ID: <3E52903B.D84890A0@snf.stanford.edu> Labmembers, I would like to take a moment to thank Colby Bellew for an action taken last week when he noticed a wbdiff hot pot that was in trouble and notified staff member Jim Haydon. This is an excellent example of a conscientious user and community spirit which is the heart of our fab operations. Thank you, Colby Bellew. The wbdiff hot pot in question had its fluid level lowered to the top of the heater band. The low fluid level sensor failed. With the heater left on, the sulfuric/peroxide mix was locally boiling and presented a potential splash hazard and, ultimately, a potential fire hazard. Since the temperature sensor was no long submerged, the heater controller was applying full power. The fluid level sensor line (the N2 bubbler) had condensed fluid in it which gave a false indication of a full pot. A klixon over-temperature sensor switch would still have provided the second level of fire protection. Level sense lines have checked, cleared or replaced in wbdiff and wbsilicide. Wbnonmetal and wbmetal are next in line for checking. Always disable the bench when you are finished. If the next user already has an operation in progress, have them enable over you. Thanks, Dick Crane From rcrane at snf.stanford.edu Tue Feb 18 17:17:22 2003 From: rcrane at snf.stanford.edu (Dick Crane) Date: Tue, 18 Feb 2003 17:17:22 -0800 Subject: Painting schedule Message-ID: <3E52DB22.CAB27ED8@snf.stanford.edu> CIS/CISX building dwellers, Here is the latest schedule for the building painting/detailing work. First Floor Common Areas of CIS (including lobby restrooms) Start Date: Monday, February 10 Completion date: Tuesday, February 18 Second Floor and Stairways of CIS Start Date: Tuesday, February 18 Completion Date: Friday, February 21 West stairs: Friday, February 21 East stairs: Monday, February 24 CIS115: Thursday, February 20, 0630-1030 CIS201: Monday, February 24, 0630-1030 First Floor Common Areas of CISX Start Date: Monday, February 24 Scope Areas to be painted include: Common areas outside offices and conference rooms Stairways (except the maintenance stairway) SNF wall (partial) All columns Door frames ? no doors Drywall repair in front entry Lobby desk (after repair) Hours: 6:30-3:30 and weekends ? not Monday, 2/17/03 Thanks for your cooperation, Dick Crane From curlwang at stanford.edu Wed Feb 19 21:15:19 2003 From: curlwang at stanford.edu (Ke Wang) Date: Wed, 19 Feb 2003 21:15:19 -0800 (PST) Subject: used lab rack? Message-ID: Hello everybody, I'm really in need of a standard 19" lab rack. New ones seem to be quite expensive! So I'm hoping that I can find a used one around. If you happen to know one that is not being used, and can possibly let me use (or sell to me at a reasonable price), please do let me know. Thanks a lot!!! Ke _____________________________________________ Ke Wang PHD Candidate Department of Applied Physics, Stanford University CISX B113-14 Stanford, CA 94305-4070 Phone: (650)723-8040 From shott at snf.stanford.edu Thu Feb 20 11:52:32 2003 From: shott at snf.stanford.edu (John Shott) Date: Thu, 20 Feb 2003 11:52:32 -0800 Subject: Thefts and building security ... Message-ID: <3E553200.F7B8F6FC@snf.stanford.edu> SNF Lab Members and Building Occupants: Bob Wheeler just sent out the following message warning of a number of recent thefts in nearby buildings ... >Dear Department Managers, >Recently, there have been a number of thefts of computers and >research equipment from Green Earth Science and the HEPL buildings. >Please advise your staffs to be observant of unfamiliar individuals >in their areas. People should call 9-911 to report any suspicious >individuals or activities. > > >Bob ... the timing of this is particularly disturbing as I discovered on Monday morning that 3 of the exit doors to CIS/CIS-X had been propped open by chairs or newspapers. My best guess is that these doors had been propped open some time on Sunday and were open all Sunday night ... making for exceedingly easy pickings for anyone with less-than-honorable intentions. Let me remind you of a few things: 1. We've got a huge number of expensive and valuable items in this building ... and in many cases the only thing preventing unencumbered access to them is our locked exit doors. 2. There is NO legitimate reason for propping doors open when they should be locked. If there is a special event, we can make arrangements to unlock the doors during a specific time window ... which will insure that they are locked after that event. If you are meeting someone who does not have door access ... then meet them, let them in, and make sure that the door is closed. 3. If you see doors propped open, don't assume that someone has a good reason (see point 2) ... be a good citizen and close them. 4. If you have any knowledge as to the who and when of the doors being propped open this past Sunday, please contact me. I'd like to find out who is responsible so that we can correct this misunderstanding and avoid future problems. Please be aware of building security ... particularly during nights, weekends, and holidays ... the computer/cell phone/wallet that you save may be your own! Thanks for your continued cooperation, John From rcrane at snf.stanford.edu Fri Feb 21 09:47:42 2003 From: rcrane at snf.stanford.edu (Dick Crane) Date: Fri, 21 Feb 2003 09:47:42 -0800 Subject: [Fwd: Police Contact Information] Message-ID: <3E56663D.E5D48A18@snf.stanford.edu> Building and lab people, Another chapter in how to report suspicious activities to the police department. Your help in keeping the building closed and locked on weekends and after hours is greatly appreciated. Thanks, Dick Crane George Sandoval wrote: > > Zone A Building Managers, please distribute the following contact > information for Police Services to your building occupants. Although > most campus residents know that they should dial 9-911 for campus > emergencies, relatively few people know how to contact the Police for > "non-emergency" service. This is especially true on evenings and > weekends when building managers, administrative staff, and other > building support personnel are not available for assistance. Many of > the following observed activities tend not to be reported immediately > to the Police: > > - Illegal parking > - Illegal skating activities (reference attached copy of ordinance) > - public disturbances > - vandalism > - malicious mischief > - theft > - building security issues > - suspicious activities > > The University sustains costly damages resulting from the above > activities each year. The University spends a considerable amount of > money to install physical deterrence measures, where appropriate. > However, it is not practical, nor financially feasible, to prevent > these activities through physical deterrence alone. We depend on the > eyes, ears, and support of the campus community and enforcement by > Police Services. Immediate reporting is critical to successful > enforcement and prevention. Please keep the following Police contact > information near your phone(s) for future reference. Immediately > report any illegal or suspicious activities to the Police. Thank you > for your support. > > Police Contact Numbers: > > Emergency Response: 9-911 > > Non-Emergency Response (Monday - Friday; 8am-5pm): 3-9636 > Stanford University Department of Public Safety Police Services: > > Non-Emergency Response (24 hours/day; 7 days/week): 650-329-2413 > Palo Alto Police Dispatch: > > > > > > George E. Sandoval Phone: (650) 725-3670 > Fac. Ops. Zone A Mgr. Pager: (650) 301-2326 > Stanford University Fax: (650) 725-6070 > 340 Bonair Siding > Stanford, CA 94305-7273 ORDINANCE OF THE BOARD OF SUPERVISORS OF THE COUNTY OF SANTA CLARA IN THE STATE OF CALIFORNIA RESTRICTING USE OF ROLLER SKATES AND IN-LINE SKATES ON THE PROPERTY OF LELAND STANFORD JUNIOR UNIVERSITY ORDINANCE NS - 1004.134 CHAPTER IV: ROLLER SKATES AND IN-LINE SKATES Sec. B5-32 Property of the Board of Trustees of Leland Stanford Junior University Within Santa Clara County For purposes of this Chapter, "Property of the Board of Trustees of Leland Stanford Junior University within Santa Clara County" shall mean: Beginning at the intersection of El Camino Real (Highway 82) and Stanford Avenue, then going south to Peter Coutts Road, then going east to Page Mill Road, then going south to Arastradero Road, then going west to Alpine Road, then going north to Sand Hill Road, then going northeast to Arboretum Road, then going east to Quarry Road, then going north to El Camino Real (Hwy 82), then going east to the intersection of El Camino Real (Hwy 82) and Stanford Avenue. Sec. B5-33: Restricted Areas On the property of the Board of Trustees of the Leland Stanford within Santa Clara County, it shall be unlawful for any person to skate, ride or propel roller skates, in-line skates or similar devices on or within any: (a) building; (b) courtyard; (c) parking garage (structure); (d) entryway; (e) tennis court; (f) construction site; (g) stairway, railing, wall, fountain, bench or any other outdoor structure or furnishing not intended for travel. Sec. B5-34: Restricted Actions It shall be unlawful for any person to skate, ride or propel roller skates, in-line skates or similar devices on the property of the Board of Trustees of the Leland Stanford Junior University within Santa Clara County, in line the following manner: (a) Perform any tricks, stunts, any form of acrobatic actions or other actions that are likely to cause injury or damage property; (b) Travel at a speed greater than is reasonable and prudent having due regard for the pedestrian or vehicle traffic, width of the sidewalk or roadway, and in no event at a speed which endangers the safety of persons, animals or property; (c) Impede or interfere with the flow of vehicular traffic; (d) Fail to yield to all pedestrians on sidewalks or roadways, including at or in marked or unmarked crosswalks; (e) Fail to obey all stop signs, traffic signals, yield signs, and other such traffic control devices; (f) Suddenly leave a curb or other place of safety and travel into the path of a vehicle which is so close as to constitute an immediate hazard; (g) Hitch rides by attaching oneself to any vehicle or other motive device, or allow a person to hitch a ride on any vehicle or motive device. Sec. B5-35: Penalty No penalty for violation of this Chapter shall exceed One Hundred Dollars ($100). PASSED AND ADOPTED by the Board of Supervisors of the County of Santa Clara, State of California on April 28, 1998. If no frames are displayed, click this link to return to SSU Home Page 1 of 1 Stanford Police - Special Services Unit: Ordinance 2/20/2003 http://www.stanford.edu/group/ssu/ordinance.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtang at snf.stanford.edu Fri Feb 21 15:52:58 2003 From: mtang at snf.stanford.edu (Mary Tang) Date: Fri, 21 Feb 2003 15:52:58 -0800 Subject: Micromachined Tranducers Sourcebook Message-ID: <3E56BBDA.833D6BF7@snf.stanford.edu> Greeting Labmembers -- Many labmembers have discovered the deep, dark secret of the process staff -- we rely on the "Micromachined Transducers Sourcebook" (written by our very own Greg Kovacs), which is absolutely one of the most useful references for processing just about anything in the lab... We are down three copies (one of them autographed!).... If you happen to have one of our copies, could you please, please, please return it? Thanks, Mary -- Mary X. Tang, Ph.D. National Nanofabrication Users' Network Stanford Nanofabrication Facility CIS Room 136, Mail Code 4070 Stanford, CA 94305 (650)723-9980 mtang at snf.stanford.edu From shott at snf.stanford.edu Mon Feb 24 11:58:52 2003 From: shott at snf.stanford.edu (John Shott) Date: Mon, 24 Feb 2003 11:58:52 -0800 Subject: Wednesday morning Coral outage for hardware/software upgrades ... Message-ID: <3E5A797C.DF1844E2@snf.stanford.edu> SNF Lab Members: This Wednesday, February 26, we are planning on taking the Coral system down in order to upgrade the hardware/software/database on which Coral depends. This downtime is currently scheduled to start at 5 a.m. and we expect to be back on-line no later than 10 a.m. We expect to issue an equipment "all on" so that work in the lab will be minimally disturbed and hope that you will all quickly enable equipment once normal coral operations are restored. Finally, while e-mail receipt and delivery will not be affected, those of you with your primary home directories on snf/sunray may be unable to login/access that mail during this outage. We apologize for this scheduled downtime but hope that this will be an important step in assuring higher Coral availability in the future. Plus, we are hopeful that you'll appreciate several of the new features of Coral associated with this new release. Stay tuned for more details of some of those new capabilities .... Thanks for your continued support, John From yy7343 at hotmail.com Mon Feb 24 20:54:38 2003 From: yy7343 at hotmail.com (Yahong Yao) Date: Mon, 24 Feb 2003 20:54:38 -0800 Subject: looking for a paper Message-ID: Dear labmembers, I am looking for a paper presented in the Micromachining and Microfabrication of 2003 by SPIE. The conference was in late Jan. and the proceedings are not available in library yet. The paper is titled "Micropackaging Technologies for Integrated Microsystems: Applications to MEMS and MOEMS" by Professor Khalil Najafi. If any one has the proceedings, pls let me know. Thanks a lot. Regards, Yahong _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail From mahnaz at snf.stanford.edu Tue Feb 25 16:17:58 2003 From: mahnaz at snf.stanford.edu (Mahnaz) Date: Tue, 25 Feb 2003 16:17:58 -0800 Subject: Training Message-ID: <3E5C07B6.3FA65B9B@snf.stanford.edu> Hello all, I am happy to let you all know that Chad Brubaker the staff engineer from Electronic Vision will be here on Thursday 2/27. We will have the introduction to EV bonder around 9:30 in the morning in the lab. If you are requesting/planning bond training in near future, I strongly suggest to attend this session. The afternoon will be spend on EV aligner training at about 2:15 pm. If you need back side, front side training or any other question please come by at that time. See you mahnaz From shott at snf.stanford.edu Wed Feb 26 11:15:54 2003 From: shott at snf.stanford.edu (John Shott) Date: Wed, 26 Feb 2003 11:15:54 -0800 Subject: New release of Coral ... Message-ID: <3E5D126A.E96E09EF@snf.stanford.edu> SNF Lab Members: This morning, during the process of making some hardware and database upgrades, we also installed a new release of Coral that includes a handful of new features. While I won't go into the full details of how to use all of those new features in this message, I'll at least give an introduction of what you can expect: 1. Very minor change ... when your Coral client starts up, it now pops up a window that says "Coral starting ..." so that you know that something is happening. 2. The maintenance client is completely new. Features that it now adds are, most importantly, the ability to see the text of problem and shutdown reports ... and to be able to see the text of any message that was recorded during the clear of a problem or shutdown. Actually, the message length that will be displayed will be limited to 4000 characters ... but, for all but the most wordy, that should be dramatically better that the previous maintenance client that didn't show the text message at all. Of course, for people reporting problems and shutdowns, I expect that you will take advantage of this to more completely describe the symptoms of the condition that you observe. And, for the folks making equipment repairs, you can now detail what you did to fix the problem ... both for the benefit of our members and so that you have a permanent written record for the next time you encouter the same problem. No more one-word resolutions ... By default, the new maitenance client shows any unresolved problems or shutdowns that have been reported during the last 90 days. However, by entering different dates and by checking different option boxes, you can also show resolved problems and shutdowns, for example, in additon to outstanding problems and shutdowns. After selecting any specific problem or shutdown, there is button to show the full text of the problem/shutdown report as well as the text of any resolution. Note: while we may be able to backload any previous reporting/resolving text messages, at the moment, there are no text messages in the database prior to this morning. So, if you know that you submitted a problem report (including text) on Monday, it will not yet show up ... 3. The reservation client now allows you a choice: see all reservations for one piece of equipment for a two-week time window (which is the old, familiar standard) or show all of YOUR reservations for ALL pieces of equipment for a single day (by default, today, but you can move forward and backward in time by using the "Next" and "Previous" menu items in the reservation menu. This new display has two sub-panels ... in the left, you see all of your reservations for a single day with multiple columns if you have reservations on multiple pieces of equipment. On the right side, you can select one or more pieces of equipment and will see all of the reservations for the selected pieces of equipment for that day. (Hint: Control-Click will add additional pieces of equipemnt to this window and Shift-Click will add an entire range between to previous and currently selected points in the equipment hierarchy.) Also, you can make a new reservation in the right side of the new window ... the left side, however, doesn't let you make/delete reservations. This new client is reasonably complex and I won't try to fully detail exactly how to use it here ... we'll be trying to put out a more detailed description in the near future. 4. New remote client ... you will notice that Java Web Start will download a new set of Remote Coral files when you next fire it up. Not only does this add the new capabilities described above, but it also includes new encryption/decryption software that is more fully compatible with new releases of Java. Over the past serveral months, a number of you had encountered Remote Coral problems for which the fix was to find a file name "jce.jar" on your local machine and rename it to "jce.jar.ignore" ... which effectively disabled that file. If you are one of these people, you should now go in and change the name of the file jce.jar.ignore back to jce.jar which will will restore the default behavior of new versions of java. (For anyone downloading a fresh version of java, it should work with the new Remote Coral without any of this "file name tinkering ..."). 5. There is also a new panel on the Coral client called "Equipment Status Summary". If you highlight one of the areas in the lab ... for example "Dry Etching" you will see the equipment status of all of the pieces of equipment in that area including the reporting date of any unresolved problems and shutdowns. By clicking the "problem", "shutdown", or "up" button you can view any combination of up/problem/shutdown equipment in that area. Note: is is only a summary page ... if you need to clear a problem or shutdown or want to view the text of problem/problem shutdown reports, you need to go to the maintenance client. We hope that you will find some of these new features of utility. If you have any comments or feedback ... or particularly if you see any problems or bugs ... please send e-mail to coral at snf.stanford.edu. Thank your for your continued support, John and Team Coral p.s. I should also point out that several of these new features were actually implemented by the Coral developers at MIT. Our sister lab at MIT went into production with Coral about a week ago and, most importantly, have 2 software developers working on enhancements to Coral. We believe that both sites will benefit from this joint development and it is our hope that we will collectively be able to enhance Coral's capabilities at a greater rate than either school can individually. From rcrane at snf.stanford.edu Wed Feb 26 12:09:42 2003 From: rcrane at snf.stanford.edu (Dick Crane) Date: Wed, 26 Feb 2003 12:09:42 -0800 Subject: HEPA air interruption 3/8/03 Message-ID: <3E5D1F06.BDE2D236@snf.stanford.edu> All, Facilities will be upgrading the HEPA fan drive control units. This upgrade will affect the quantity of air blowing through the HEPA filter which will affect the airborne, particle count in the fab. Local area volume of air will drop to 20% of normal flow. I would estimate that our class 100 cleanroom will become a class 1000 room for a few hours. The air is clean, but the room's ability to deal with particle assaults is reduced. Processing which is very sensitive to particle contamination should be avoided in the affected areas during the upgrade work. Photo area: On Saturday, March 8, from 0700 to 1100, L102, the Nikon aisle (Nikon body 4, Ultratechs, EVG aligner and bonder, SVG coat and develop tracks) will have reduce air flow. This loss may be critical to your process. Mask making area: On Saturday, March 8, from 1200 to 1600, L106, the mask making room (Micronic, AFMs) will have reduce air flow. This loss should not affect your process. Wet bench exhaust will be unaffected. Thanks for your patience, Dick From shott at snf.stanford.edu Wed Feb 26 15:54:09 2003 From: shott at snf.stanford.edu (John Shott) Date: Wed, 26 Feb 2003 15:54:09 -0800 Subject: Remote Coral and Legion of the Bouncy Castle ... Message-ID: <3E5D53A1.1D2B6A80@snf.stanford.edu> SNF Lab Members: I've received a couple of comments from folks worrying about the warning that they get about the "Legion of the Bouncy Castle" when they download the new version of Remote Coral. The new public domain crytpography stuff that we are using is from www.bouncycastle.org (AKA the Legion of the Bouncy Castle). While I personally have no knowledge as to the origins of that name ... I do believe that they are legitimate providers of cryptography software. (Afterall, this is Silicon Valley ... I'm a little surprised at people thinking that that is a funny name for an organization in the land of startups with funny names. Maybe the lack of "Z" and "X" is their name is suspicious ...). In any event, the Bouncy Castle stuff is what we are trying to download to your machine as a part of Remote Coral because that is the package that we are using to handle encryption/decryption of your login name and remote passwords. It is flagged separately because it is signed by Sun whereas Remote Coral proper is signed by us ... So, it is certainly my belief that the Bouncy Castle stuff is legitimate, safe, and "for real" ... but, as is often the case, the ultimate decision as to whether you want that downloaded to your machine is yours. Of course, if you don't ... Remote Coral won't run ... Thanks for your observant responses, John Note: Team Coral has no affiliation with the Legion of the Bouncy Castle (finacial or otherwise ...) other than that is the encryption/decryption package that we use because it is one of the few packages offering public domain RSA encryption. From mahnaz at snf.stanford.edu Thu Feb 27 08:39:52 2003 From: mahnaz at snf.stanford.edu (Mahnaz) Date: Thu, 27 Feb 2003 08:39:52 -0800 Subject: EV Visit Message-ID: <3E5E3F58.EE833B41@snf.stanford.edu> Kind reminder, Hello all, I am happy to let you all know that Chad Brubaker the staff engineer from Electronic Vision will be here on Thursday 2/27. We will have the introduction to EV bonder around 9:30 in the morning in the lab. If you are requesting/planning bond training in near future, I strongly suggest to attend this session. The afternoon will be spend on EV aligner training at about 2:15 pm. If you need back side, front side training or any other question please come by at that time. See you mahnaz From mahnaz at snf.stanford.edu Fri Feb 28 16:02:19 2003 From: mahnaz at snf.stanford.edu (Mahnaz) Date: Fri, 28 Feb 2003 16:02:19 -0800 Subject: EV bonder Message-ID: <3E5FF88A.EB564AE7@snf.stanford.edu> Hello all, This afternoon the 4" load glass frame for the EV bonder broke. I have a student here from Austin to use the bonder over the weekend. Any one out there have a glass frame with 3 pt. vacuum? if yes, can I borrow it . I will give you mine when arrives next week. mahnaz From mtang at snf.stanford.edu Fri Feb 28 18:49:09 2003 From: mtang at snf.stanford.edu (Mary Tang) Date: Fri, 28 Feb 2003 18:49:09 -0800 Subject: Lab Fatigue... Message-ID: <3E601FA5.EB5AF4D1@snf.stanford.edu> Labmembers: It's awfully tempting to work long hours in the lab, without break, if you're on the verge of a breakthrough or if you've got an impending deadline... However, we've had a couple of incidents (or near-incidents) recently in the lab which could have been avoided if the people involved hadn't been excessively tired or hungry. In fact, one of the most common explanations for simple mistakes is that we staff members hear is "I didn't know, it was late, and I was tired..." As I'm sure you know, such mistakes could result in damage to your experiment, damage to equipment, or worse yet, safety hazards to you or your fellow labmembers... At the risk of sounding like I'm practicing for the "mom" thing... Please take a break from the lab every few hours. Don't work without eating regularly (the hospital cafeteria, like SNF, is open 24/7). If you're tired, there are several comfy couches located throughout the office area... Also remember, we do have a "buddy rule" -- don't work in the lab unless there's also someone else in there too, or at least someone nearby who knows you're in there. Thanks for your attention -- Mary -- Mary X. Tang, Ph.D. National Nanofabrication Users' Network Stanford Nanofabrication Facility CIS Room 136, Mail Code 4070 Stanford, CA 94305 (650)723-9980 mtang at snf.stanford.edu