From shott at snf.stanford.edu Tue Jan 2 17:22:36 2001 From: shott at snf.stanford.edu (John Shott) Date: Tue, 02 Jan 2001 17:22:36 -0800 Subject: No acid/base dumping tonight .... Message-ID: <3A527EDC.9CA88DE6@snf.stanford.edu> SNF Lab Members (and people associates with other labs in CIS-X) .... The building acid/base neutralization system has failed and we are currently unable to raise/lower the pH of our waste stream. Please do not dump any acids or bases until this situation is rectified!!! If we continue to dump those materials without proper treatment, we will violate Palo Alto hazardous waste discharge rules ... which could result in big time problems, fines, and shutdowns. We apologize for the inconvenience that this may cause and will keep you apprised as we bring the system back on-line. Thank you for your cooperation and support, John From rcrane at snf.stanford.edu Wed Jan 3 11:27:54 2001 From: rcrane at snf.stanford.edu (Dick Crane) Date: Wed, 03 Jan 2001 11:27:54 -0800 Subject: Acid/base neutralizer OK Message-ID: <3A537D3A.E04CC4C9@snf.stanford.edu> SNF Lab Members (and people associated with other labs in CIS-X) .... The building acid/base neutralization system has been repaired and is fully operational. It is now available for normal use. Thanks for your cooperation, Dick From shott at snf.stanford.edu Sun Jan 7 19:18:49 2001 From: shott at snf.stanford.edu (John Shott) Date: Sun, 07 Jan 2001 19:18:49 -0800 Subject: Intermitten failure of Coral .... Message-ID: <3A593199.6405A505@snf.stanford.edu> SNF Lab Members: We are working on a subtle problem that causes the equipment hiearchy of coral to show areas, and sub-areas, but doesn't show any individual pieces of equipment. This does not show up initially after the servers have been restarted ... but then begins to crop up after about an hour. Unfortunately, we have been unable to duplicate this on our development machine. We are working hard to track down the source of the problem ... however, because people can't enable or disable equipment, or make any reservations after the equipment listings fail to show up, we are currently automatically restarting the servers every hour, on the hour, in the hopes that you will be minimally inconvenienced. We hope that this will not be in effect for long ... but ask for your indulgence and patience during this troubleshooting period. We are doing extensive logging to help pinpoint the cause of these problems ... but that also requires that we run things long enough for something to break in order to track down what is causing this problem. So, if you run into problems ... you should only have to wait until the next hour (e.g., 7 a.m., 8 a.m., 9 a.m., etc.) for things to be reset. Thanks for your patience, The Coral Development Team From shott at snf.stanford.edu Tue Jan 9 16:45:38 2001 From: shott at snf.stanford.edu (John Shott) Date: Tue, 09 Jan 2001 16:45:38 -0800 Subject: Stable version of Coral is back! Message-ID: <3A5BB0B2.9CA3B40@snf.stanford.edu> SNF Lab Members: We have re-installed the old, stable version of Coral ... you should not experience any further outages (well, at least until we begin experimenting again ...). We apologize for the downtime of the past day or so ... the reason for the failure is still a mystery to us. Extensive logging has shown us where things were breaking ... but we have been unable to determine why they are breaking. Unfortunately, we only observe this breakage when we move to the production system ... we have been unable to observe the same problems on our development machines. In any event ... life should be better for you now. If anyone has manually enabled any of the machines for you, you should enable them in your own name immediately: If the machine is enabled in reality, but Coral doesn't know it, please enable it in your name ... this should synchronize the coral database and the hardware. If Coral thinks that something is enabled and yet the actual interlock isn't "ON", disable that piece of equipment on Coral ... that should also synchronize the database, and then proceed with normal operations. Once again, we apologize for the inconvenience this has caused, Thanks for your continued support, Your Coral Development Team From ibrahim at Stanford.EDU Thu Jan 11 11:53:49 2001 From: ibrahim at Stanford.EDU (Nabeel Robert Ibrahim) Date: Thu, 11 Jan 2001 11:53:49 -0800 (PST) Subject: wafers removed during cleanup Message-ID: <200101111953.f0BJrnd24974@saga11.Stanford.EDU> Some of my wafers that I now need were removed during the most recent lab cleanup. They were placed in cardboard boxes near the rear entrance of the lab, however, the boxes which contained my wafers are no longer there. Does anyone know where I could find them? Nabeel From king at snf.stanford.edu Thu Jan 11 13:00:25 2001 From: king at snf.stanford.edu (Robin King) Date: Thu, 11 Jan 2001 13:00:25 -0800 (PST) Subject: CIS's Jacques Beaudouin Makes News Message-ID: Dear Lab Members, This article recently appeared in the Silicon Valley Magazine and may be of interest to lab members. It credits Jacques Beaudouin, retired CIS Chief Engineer, with bringing recognition to the real birthplace of Silicon Valley-- a small lab in Mountain View where Bill Shockley and his team developed the transistor. I was fortunate enough to attend the dedication ceremony and talk with some of the people who earned their place in history. Besides Beaudouin, Stanford's Prof. James Gibbons also worked with Shockley at the San Antonio Road site. For those new to CIS, Jacques Beaudouin was also instrumental in conceptualizing and building the CIS building and our state-of-the-art lab, where so many emerging new technologies continue to change the world. The story may be found at: http://www.svmagazine.com/2000/week25/Buzz/Story02.html From shott at snf.stanford.edu Thu Jan 11 16:16:49 2001 From: shott at snf.stanford.edu (John Shott) Date: Thu, 11 Jan 2001 16:16:49 -0800 Subject: Remote Coral for Internet Explorer users ... Message-ID: <3A5E4CF1.83ADA3D5@snf.stanford.edu> SNF Lab Members: I believe that some of you who are Internet Explorer users may have been having trouble getting Java WebStart downloaded ... and keep on getting the "You need to download Java WebStart" where the "Download Remote Coral" message should be. In most cases, I believe that you have likely downloaded Java WebStart correctly ... but, there was a typo in the script that detects whether Java WebStart is installed that affected Internet Explorer but not Netscape. That has now been corrected ... so, I'm hopeful that you Internet Explorer users will now be able to happily download and run Remote Coral. (Of course, if the cache of already visited Web pages on your machine contains the wrong file, you will need to purge those cached files or reload the Remote Coral page to get the proper one.) Thanks for your continued support, Your Coral Development Team From rcrane at snf.stanford.edu Fri Jan 12 10:58:31 2001 From: rcrane at snf.stanford.edu (Dick Crane) Date: Fri, 12 Jan 2001 10:58:31 -0800 Subject: New Hires Message-ID: <3A5F53D7.C3B50FF@snf.stanford.edu> Members of the lab community, I would like to announce the hiring of two new maintenance employees and the permanent hiring of an current, temporary employee. Mike Dickey comes to us with 10 years experience from North American Philips. Mike has lots of quartzware/LPCVD experience and will be working in the diffusion area. Jim Haydon comes to us with 13 years experience from several Stanford labs. Jim will be working in the high vacuum areas, mostly in thin film. He will also be looking after the DI plant and wet benches. Raphael Miranda has been working with Tony in the Receiving/Stores/Property Control area since September, 2000 on a temporary basis. Raphael has worked at Stanford for four years and is now a permanent employee at SNF. When you see the fellows around the fab, give them a "Welcome aboard". Thanks, Dick Crane Technical Director Stanford Nanofabrication Facility From mtang at snf.stanford.edu Tue Jan 16 10:20:28 2001 From: mtang at snf.stanford.edu (Mary Tang) Date: Tue, 16 Jan 2001 10:20:28 -0800 Subject: Web Pages Changes Message-ID: <3A6490EC.DF3BD08@snf.stanford.edu> Fellow Labmembers -- here are recent changes to the website: Contact info for Jim Haydon and Mike Dickey (welcome!) "Staff" contact button on the top menu bar (Dan Grupp's suggestion) Tylan recipes are now available through the web (thanks to Brian Greene) Nikon alignment marks procedure and TBD files now available on this site (thanks to Matt Hopcroft) Many thanks for everyone's inputs and suggestions. Please keep them coming. 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 rcrane at snf.stanford.edu Tue Jan 16 14:50:43 2001 From: rcrane at snf.stanford.edu (Dick Crane) Date: Tue, 16 Jan 2001 14:50:43 -0800 Subject: Neutralizer Message-ID: <3A64D043.ACE5D9ED@snf.stanford.edu> Bad news. The NaOH line to the acid waste neutralizer is still frozen. O & M is continuing to heat the lines. Looks like no waste dumping until tomorrow. Dick Crane From king at snf.stanford.edu Tue Jan 16 15:02:21 2001 From: king at snf.stanford.edu (Robin King) Date: Tue, 16 Jan 2001 15:02:21 -0800 (PST) Subject: Neutralizer In-Reply-To: <3A64D043.ACE5D9ED@snf.stanford.edu> Message-ID: The flashing yellow light wasn't coming on in the lab as it normally would when we can't dump acids. This email is a warning to not rely on the lights. Do not dump any acids or bases down the drain until staff says otherwise. Robin King On Tue, 16 Jan 2001, Dick Crane wrote: > Bad news. The NaOH line to the acid waste neutralizer is still frozen. O > & M is continuing to heat the lines. Looks like no waste dumping until > tomorrow. > > Dick Crane > From beckwith at snf.stanford.edu Tue Jan 16 15:09:16 2001 From: beckwith at snf.stanford.edu (Sharleen Beckwith) Date: Tue, 16 Jan 2001 15:09:16 -0800 Subject: Neutralizer In-Reply-To: References: Message-ID: At 3:02 PM -0800 1/16/01, Robin King wrote: >The flashing yellow light wasn't coming on in the lab as it normally would >when we can't dump acids. This email is a warning to not rely on the >lights. Do not dump any acids or bases down the drain until staff says >otherwise. > >Robin King > >On Tue, 16 Jan 2001, Dick Crane wrote: > >> Bad news. The NaOH line to the acid waste neutralizer is still frozen. O >> & M is continuing to heat the lines. Looks like no waste dumping until >> tomorrow. >> > > Dick Crane I believe this also means you cannot rinse your wafers in the dump rinsers, as per my discussion with Dick Crane at ~ 2:30 pm. Just to make sure everyone knows they should not be cleaning and/or etching wafers and using the dump rinsers to rinse them (or rinsing them in beakers at any of the "manual" wet benches). The signs on the lab doors are not clear about this. Sharleen From rcrane at snf.stanford.edu Tue Jan 16 18:54:37 2001 From: rcrane at snf.stanford.edu (Dick Crane) Date: Tue, 16 Jan 2001 18:54:37 -0800 Subject: Neutralizer Woes Message-ID: <3A65096D.F3076390@snf.stanford.edu> The neutralizer is still down. We have a plan for tomorrow morning. I hope to be operational by noon unless some damage to the transport lines is discovered. Dick Crane From latta at snf.stanford.edu Wed Jan 17 09:25:18 2001 From: latta at snf.stanford.edu (Nancy Latta) Date: Wed, 17 Jan 2001 09:25:18 -0800 (PST) Subject: Please return training tapes Message-ID: Folks, If you have any of the training video tapes for dry etching in you possession please return them as soon as possible. There are labmembers waiting to view them. Thanks! Nancy From rcrane at snf.stanford.edu Wed Jan 17 10:33:02 2001 From: rcrane at snf.stanford.edu (Dick Crane) Date: Wed, 17 Jan 2001 10:33:02 -0800 Subject: Neutralizer update Message-ID: <3A65E55E.C7D5BAFE@snf.stanford.edu> Lab members, The ice blockage has been removed in the tranfer lines are being tested presently. Unless there are further problems, we should be operational by noon today (1/17). Why can't we dump water if the amber lights are off? The neutralizer has a continuous water load. The amber lights are not on because the pH is within limits. If bottle washing, wafer processing or other cleaning activities changes the pH to outside the limits, then the system shuts down even further and I have additional problems. The problem of blocked NaOH lines is an unusual one and not planned for. Thanks for your cooperation and patience. Dick Crane From mahnaz at snf.stanford.edu Wed Jan 17 10:45:58 2001 From: mahnaz at snf.stanford.edu (Mahnaz Mansourpour) Date: Wed, 17 Jan 2001 10:45:58 -0800 Subject: KS update Message-ID: <3A65E866.F2A1600A@snf.stanford.edu> Hello all, As you all know our famous KS has been down big time for digital video control unit and for BSA repair. I have been talking to KS people a lot recently trying to get the part # for the parts and this morning the person whom I am dealing with KC Colt told me that they are doing their best to put these stuff together. I did mention that two weeks is awfully long to get these data and she said they are very busy and I should wait for them to send me the the information. If you want to voice your opinion or talk to some one, here are the information. Klaus Ruhmer is the application Engineer for the region He can be reached at 408-432-3071 602-557-9370 ext. 114 Mahnaz From rcrane at snf.stanford.edu Wed Jan 17 10:54:48 2001 From: rcrane at snf.stanford.edu (Dick Crane) Date: Wed, 17 Jan 2001 10:54:48 -0800 Subject: Neut Update Page 2 Message-ID: <3A65EA78.CF2B66A7@snf.stanford.edu> Lab members, Lab turn-on time has been pushed back to this afternoon. Two of the four NaOH have damaged seals. They are currently being replaced. As soon as they are operational the fab will be ready for use. Dick Crane From mahnaz at snf.stanford.edu Wed Jan 17 11:11:03 2001 From: mahnaz at snf.stanford.edu (Mahnaz Mansourpour) Date: Wed, 17 Jan 2001 11:11:03 -0800 Subject: Ev visit and bonding presentation Message-ID: <3A65EE47.E15CBE73@snf.stanford.edu> Hello all, Chad Brubaker an staff engineer from EV will be here on Thursday February 8th. We will spend the morning in the lab so if you have any question about the aligner or the Bonder please come by. Chad will be giving a presentation about anodic and fussion bonding in the afternoon. I think we all can benefit from that as more and more people are using the bonder. So please try to attend the talk and let other interested users know about it too. I made reservation for February 8th. from 2-4 in CIS 101. mahnaz -------------- next part -------------- An HTML attachment was scrubbed... URL: From mahnaz at snf.stanford.edu Wed Jan 17 13:18:50 2001 From: mahnaz at snf.stanford.edu (Mahnaz Mansourpour) Date: Wed, 17 Jan 2001 13:18:50 -0800 Subject: Resist presentation Message-ID: <3A660C3A.7421C8B7@snf.stanford.edu> Hello all, I am very pleased to announce that Dr. Frank Yaghmaie of Shiply has accepted to give a talk in the area of i-line resist. I have expressed more and more lab members are using glass and quartz wafers and he will talk about different method like, FSC, face shield coverage and the benefit of dye in the resist. The talk will be on Friday February 2nd. at 2 pm Auditorium 101x mahnaz -------------- next part -------------- An HTML attachment was scrubbed... URL: From FYaghmaie at Shipley.com Tue Jan 16 16:41:35 2001 From: FYaghmaie at Shipley.com (FYaghmaie at Shipley.com) Date: Tue, 16 Jan 2001 19:41:35 -0500 Subject: Resist presentation Message-ID: Mhanaz, I will be glad to do my yearly talk, will focus on critical and noncritical i-line. I am sure we will get into the use of glass substrates as it relates to Fiber optics as well. Plan to spend 60 minutes on the resist and as usual hr or so on the resist processing with IC labs industrial partners. Best Regards Frank Mahnaz Mansourpour To: Lab , , headway at snf.stanford.edu cc: 01/17/01 04:18 Subject: Resist presentation PM Hello all, I am very pleased to announce that Dr. Frank Yaghmaie of Shiply has accepted to give a talk in the area of i-line resist. I have expressed more and more lab members are using glass and quartz wafers and he will talk about different method like, FSC, face shield coverage and the benefit of dye in the resist. The talk will be on Friday February 2nd. at 2 pm Auditorium 101x mahnaz From beckwith at snf.stanford.edu Wed Jan 17 17:57:22 2001 From: beckwith at snf.stanford.edu (Sharleen Beckwith) Date: Wed, 17 Jan 2001 17:57:22 -0800 Subject: reservation of the wet bench starting at 9 am Message-ID: Folks: I know, people will want to be using the wet bench tomorrow, but we still have to do the super clean device run that was cancelled last week. Therefore, we would like to have use of the bench stating at 9:00 am to cool down the hot pots. I will be starting the clean at noon. When I am done the bench will be open for business as usual. Please let me know if this is a problem for anyone. Sharleen From beckwith at snf.stanford.edu Wed Jan 17 18:33:12 2001 From: beckwith at snf.stanford.edu (Sharleen Beckwith) Date: Wed, 17 Jan 2001 18:33:12 -0800 (PST) Subject: update on the neutralization system Message-ID: Folks: Tony and Jose were here until after 6:30 pm working on the neutralization system. The pump is now not working. Tony said they will start working on the pump first thing in the morning. Just thought everyone would want to know the latest. Sharleen From shott at snf.stanford.edu Thu Jan 18 10:23:18 2001 From: shott at snf.stanford.edu (John Shott) Date: Thu, 18 Jan 2001 10:23:18 -0800 Subject: Acid Netralization system ... provisional usage. Message-ID: <3A673496.1720AD81@snf.stanford.edu> SNF lab members: The acid/base neutralization system is not yet fully (and automatically) operational ... but we are able to begin to dump acids PROVIDED the following guidelines are used: Prior to dumping any of the hot pots (or acids at WB general), contact one of the maintenance staff members, Dick Crane, or me. One of us will go down to the acid neutralization system and monitor the pH in the tanks and make adjustments accordingly. It is essential that one of us be down there to monitor the pH prior to any dumping activity! We apologize for this inconvenience but feel that it is important that we do what we can to get the lab operational once again. Please adhere carefully to these guidelines ... even a brief excursion beyond the legal pH limits will require us to shutdown completely until the neutralization system is fully operational. Thanks for your continued support, John From shott at snf.stanford.edu Thu Jan 18 11:51:41 2001 From: shott at snf.stanford.edu (John Shott) Date: Thu, 18 Jan 2001 11:51:41 -0800 Subject: Acid neutralization addendum ... sulfuric acid. Message-ID: <3A67494D.401AEAB5@snf.stanford.edu> SNF labmembers: Two additional points related to acid dumping and neutralization that I forgot to mention: 1. You do not need to nofify us of use of dump rinsers or use of SVG developers. 2. We have to be particularly careful when dumping sulfuric acid. If we compare dumping equal hot pot volumes of 5:1:1 H2O:H2O2:HCl vs. 9:1 H2SO4:H2O2 we find that the amount of neutralization that has to be done in the case of the HCL hot pot is proportional to 1/7 * 0.37 which is about 0.05. The 1/7 is due to the fact that only one part in seven of the total mixture is actually HCL and the HCl that we use is about 37% concentration. One of the 9:1 H2SO4:H2O2 pots, however requires total neutralization that is proportional to 9/10 * 0.96 *2 which is about 1.7. In this case, the volume of our mixture is about 90% sulfuric acid, plus the strength of sulfuric acid straight out of the bottle is approximately 96%. Finally, because there are 2 hydrogen ions in each H2SO4 molecule, we have to neutralize each of them. In other words, dumping one of our sulfuric hot pots requires approximately 35 times more neutralization "effort" than an equivalent 5:1:1 HCl hot pot. So be extra careful to warn us if you are about to dump a sulfuric hot pot! Thank you for your continued support ... John From king at snf.stanford.edu Thu Jan 18 13:13:40 2001 From: king at snf.stanford.edu (Robin King) Date: Thu, 18 Jan 2001 13:13:40 -0800 (PST) Subject: GaAs Wetbench SHUTDOWN NOTICE Message-ID: The GaAs acid wetbench is shut down because someone left in an unsafe, unacceptable condition: 1) The plastic side panels were removed. 2) There are BHF(?) crystals around the bench. 3) A small beaker and wafer holder was left with an unidentified liquid in it. 4) A quartz beaker was broken and left in the bottom of the sink 5) Other beakers were left on their sides in the bottom of the sink. 6) The hot plate was left on and unattended, a fire hazard. It's unthinkable that anyone can be so careless The last person to sign up for that bench was not the person who did this so someone is also breaking the rules by not signing up. If you contributed to this please come in and take care of it immediately. The entire bench needs to be cleaned up, rinsed and wiped down. If you needed to use the wetbench please direct your frustration to those responsible for the mess. Robin King From rcrane at snf.stanford.edu Fri Jan 19 20:54:50 2001 From: rcrane at snf.stanford.edu (Dick Crane) Date: Fri, 19 Jan 2001 20:54:50 -0800 Subject: Waste Neutralizer Chapter3 Message-ID: <3A691A1A.88B160AD@snf.stanford.edu> After numerous issues, pumps and fittings, I believe the acid/base waste neutralizer system to be operational. Hot pots can now be dumped at will and the system will deal with it automatically. Thanks for your help and patience and have a good weekend. Dick Crane From mtang at snf.stanford.edu Mon Jan 22 17:47:02 2001 From: mtang at snf.stanford.edu (Mary Tang) Date: Mon, 22 Jan 2001 17:47:02 -0800 Subject: Labmember Survey Message-ID: <3A6CE296.F9163B4C@snf.stanford.edu> Dear Labmembers: The SNF staff and the newly formed faculty SNF Advisory Committee recognize that there are problems which may have adversely affected your ability to do research here. In an effort to gage the current and future needs of our labmember community, we ask that you contribute by providing us with feedback on your experiences and opinions on how the lab is meeting your research needs. We ask that you fill out and return the Labmember Survey form, taking time to elaborate as you see fit. This survey is anonymous. This results will be used by the staff and the Advisory Committee to set the agenda and priorities for the lab. Your honest, constructive, feedback is vital. Blank survey forms are available outside the lab entrance and online at the SNF website (http://snf.stanford.edu). Forms may be returned to the labeled box, outside the lab entrance, or by mail to: Labmember Survey Attn: Sandy Plewa CIS-X Room 203X, Mail code 4075 Stanford University Stanford, CA. 94305-4075 Please return responses by Monday, February 5, 2001. Responses will be then tabulated and summarized for all labmembers to review. Thank you for your help, The SNF Staff and Advisory Committee From shott at snf.stanford.edu Tue Jan 23 10:04:29 2001 From: shott at snf.stanford.edu (John Shott) Date: Tue, 23 Jan 2001 10:04:29 -0800 Subject: SSH access to/from snf and sunray ... Message-ID: <3A6DC7AD.9FF11592@snf.stanford.edu> SNF Lab Members: To be more compatible with a broader range of ssh (secure shell) applications, we have recently upgraded the ssh clients and servers on sunray and snf. In the process, I discovered that support for the older ssh1 protocol is rapidly disappearing. While we currently support both ssh1 and ssh2 protocols on our machines (with a primary use of ssh2 that gracefully fails over to ssh1 when required), it is apparent that future versions of ssh clients/servers are increasingly likely to only support the newer ssh2 protocols. As a result, those of you who are using ssh to get into either snf or sunray or to get from snf or sunray to other machines should check which version those other machines are running ... and see if they can upgrade it they find that it is the older ssh1 protocol. If you are on a remote host, you should be able to check this by issuing the command "ssh -V" which should give you the version of the ssh client on that machine. (Note: I can't guarantee that the "ssh -V" syntax returns the version information for all ssh clients, but it should on most ...). If you are using ssh from snf or sunray to get to another machine, you should be able to tell if it is running a ssh1 server on that host ... if it does it will say something like: "warning: executing /usr/local/bin/ssh.old for ssh1 compatability." Please check which version you are either using or connecting to and please let me know if you find that you are either using a ssh1 client or connecting to a machine that only supports ssh1 ... I'd like to get a sense of how may folks are in that camp. Thank you for your continued support, John From beckwith at snf.stanford.edu Tue Jan 23 12:32:11 2001 From: beckwith at snf.stanford.edu (Sharleen Beckwith) Date: Tue, 23 Jan 2001 12:32:11 -0800 Subject: old quartz wafers you no longer want Message-ID: Folks: Do you have some old quartz wafers you no longer want? If so, could I have them. I would like to use them for some exposure experiments. Thanks. Sharleen From mahnaz at snf.stanford.edu Tue Jan 23 13:10:16 2001 From: mahnaz at snf.stanford.edu (Mahnaz Mansourpour) Date: Tue, 23 Jan 2001 13:10:16 -0800 Subject: chemicals Message-ID: <3A6DF338.DAFFAD54@snf.stanford.edu> To whom ever is responsible!!! Some one has left 3 different bottle of chemical in the cart in the lab. The chemicals do not have a yellow label on them for one. They left in the cart in the litho area for all the morning. Who ever you are, come and see me. This is totally unacceptable, and I will get rid of them before I go home. You are not following the lab policy. mahnaz From mahnaz at snf.stanford.edu Tue Jan 23 14:44:23 2001 From: mahnaz at snf.stanford.edu (Mahnaz Mansourpour) Date: Tue, 23 Jan 2001 14:44:23 -0800 Subject: [Fwd: chemicals] Message-ID: <3A6E0947.8B4C38B9@snf.stanford.edu> The Chemicals are cyclohexanone negative resist NR7-1500P and developer RD6 mahnaz -------------- next part -------------- An embedded message was scrubbed... From: Mahnaz Mansourpour Subject: chemicals Date: Tue, 23 Jan 2001 13:10:16 -0800 Size: 1453 URL: From mahnaz at snf.stanford.edu Wed Jan 24 12:23:54 2001 From: mahnaz at snf.stanford.edu (Mahnaz Mansourpour) Date: Wed, 24 Jan 2001 12:23:54 -0800 Subject: Up date Message-ID: <3A6F39DA.B26D454C@snf.stanford.edu> Hello all, Just to let you know what is happening with our Karl Suss. I finally got the quote and the part # yesterday around lunch time. Yesterday morning I had a voice mail from Klaus of KS that saying that they are waiting for our P.O #. I left him a message saying that I still have no part#. before I know it I had a copy in. Thanks to those people who took the time and called him, he said this was unacceptable from their part. We did an urgent P.O yesterday, the amount is large. One item is about $10,000 and the other $ 6000. The parts still need to be shipped to us from Germany. Thanks for being so patient.. mahnaz From shott at snf.stanford.edu Wed Jan 24 15:17:52 2001 From: shott at snf.stanford.edu (John Shott) Date: Wed, 24 Jan 2001 15:17:52 -0800 Subject: Remote checking of tylan furnaces ... Message-ID: <3A6F62A0.7BAA0399@snf.stanford.edu> SNF Lab Members: I believe that we have been able to revive the old computer that talks to the tylan furnaces one more time. As a result, I beleive that you should be able to use the old crystal wand to check on furnace status and download recipes once again. This all runs on an ancient DEC computer on a long-unsupported operating system ... Compaq would laugh if we called to ask about support or spare parts ... In any event, if you see them, you can thank Mike Bell and Charlie Orgish for their efforts in getting this back on the air. Happy processing ... John p.s. Some of the dates may be a bit "funky" ... the machine lattice thinks that it is Dec. 26 and, if I am not mistaken, the tylan computer believes that it is January 6, 1982. From mbell at snf.stanford.edu Thu Jan 25 15:19:30 2001 From: mbell at snf.stanford.edu (Mike Bell) Date: Thu, 25 Jan 2001 15:19:30 -0800 Subject: Coral System Update Message-ID: <3A70B482.5602DAE7@snf.stanford.edu> Members, The Coral system will be down for minor reconfiguration purposes between 6 AM and 7 AM tomorrow, Friday, January 26th. Sorry for any inconvenience this causes. Mike Bell SNF Staff 725-9503 From mtang at snf.stanford.edu Fri Jan 26 18:49:58 2001 From: mtang at snf.stanford.edu (Mary Tang) Date: Fri, 26 Jan 2001 18:49:58 -0800 Subject: Labmember Survey Message-ID: <3A723756.92FA2910@snf.stanford.edu> Labmembers: Survey results thus far are full of constructive criticisms, insight and, shall we say, passion. They will undoubtedly be of great interest to our faculty advisory committee. Please keep them coming. Results (including comments) of surveys collected by Monday, Feb. 5 will be posted on the website. Due to popular demand, there is an electronic, Word compatible version on the web for those of you with a lot to say (follow the links from the SNF home page -- sorry, it's a bit cludgey, but I'm no programmer -- if you prefer to be emailed the Word file, send me a note.) And yes, if you would rather save a tree (and my fingers, as I''ll be transcribing results), a floppy disk put in the collection box would be fine. Keep the surveys coming! Mary From grupp at snow.stanford.edu Mon Jan 29 19:55:49 2001 From: grupp at snow.stanford.edu (Dan Grupp) Date: Mon, 29 Jan 2001 19:55:49 -0800 (PST) Subject: Technician Position Available - FINDER'S FEE Message-ID: TECHNICIAN - I am looking for a Technician to join our dynamic team at SNF working on an advanced MOS device. We are a solidly funded startup, part of Acorn Technologies, a rapidly growing technology incubator. We offer full benefits, aggressively competitive salaries, pre-IPO stock options, and a great work environment (great people, sushi on Mondays...). FINDER'S FEE - 2% of new hire's first year salary (i.e., more than a grand). Self-referral ok. Thanks in advance, Dan --------------------------------------------------------------------------- Dr. Daniel Grupp, Visiting Scholar Acorn Technologies, Device Development Group Center for Integrated Systems Stanford University Stanford, CA 94305 (650) 724-6911 FAX: 723-4659 --------------------------------------------------------------------------- From shott at snf.stanford.edu Tue Jan 30 13:54:28 2001 From: shott at snf.stanford.edu (John Shott) Date: Tue, 30 Jan 2001 13:54:28 -0800 Subject: Minor Coral Upgrades ... Message-ID: <3A773814.95CA3D17@snf.stanford.edu> SNF Lab Members: We are going to install a slightly modified version of the Coral clients and servers this afternoon ... and will likely install a second set of modifications later this week. Those of you running Coral remotely will have to download and install the new client ... and, in fact, the old client won't work once the new servers are in place. While Java Web Start should make this a painless process, we apologiize for any inconvenience that it may cause. Without boring you with too many of the underlying details, let me explain why we needed to make some changes ... and where performance should inprove with these changes: One of the "behind the scenes" elements of Coral is something called the event manager. The event manager is basically an information clearing house that notifies all of the existing clients anytime anything "interesting" happens so that they can update their displayed information. For example, everytime that you enable a piece of equipment, all clients need to be informed that "Member x has enabled equipment y" so that the piece of equipment is shown on all clients as being enabled (by listing your name in parentheses following the equipment name). Things get updated every time a reservation is made/deleted, equipment is enabled/deleted, or a problem or shutdown is reported/cleared. As the lab has gotten busier and, in particular, because we typically have a number of remote clients to notify in addition to all of the sessions running in the lab, the performance of the event manager has begun to be a bottleneck. You may have noticed this: the delay between when you click "OK" to make a reservation and when it actually shows up on your screen is the time that the event manager is notifying all clients. While it is often a very short delay ... sometimes it is annoyingly long. This afternoon, we are releasing a version of Coral that has a "new and improved" event manager ... and we have it instrumented so we can measure the time that it takes to notify people so that we can monitor whether we have improved the notification times significantly. As a secondary matter, not everyone exits Coral "cleanly" by clicking "Exit" on the upper left pulldown menu labelled "Window". When people exit properly, their client tells the event manager "Don't bother to update me anymore". However, when people exit "less gracefully" ... by just killing the window, clicking the Sun CDE Exit button at the bottom of the screen, or because of rolling brown-out ...the event manager doesn't know that a session is gone and it continues to try to notify these sessions everytime ... which slows everything down. As a result, phase 2 of this upgrade is an improved means of detecting when a client has disappeared (for whatever reason) and removing it from the notification list. That is the upgrade that we hope to install later this week. So, while we apologize for any inconvenience that these upgrades may cause, we hope that you will all begin to notice the improved response time that these changes should produce. If you have any problems or questions, please don't hesitate to contact us. Thanks for your continued support, Your Coral Development Team coral at snf.stanford.edu From shott at snf.stanford.edu Wed Jan 31 08:19:19 2001 From: shott at snf.stanford.edu (John Shott) Date: Wed, 31 Jan 2001 08:19:19 -0800 Subject: Enable/disable problems ... Message-ID: <3A783B07.B1C79B31@snf.stanford.edu> SNF Labmembers: Apparently one of the boards that enables/disables equipment has drifted out of calibration ... I'm going down to replace it with a spare, but enabling/disabling will be down for a few minutes while I do that. (I'll not shut things down until I make the swap so, hopefully, actually downtime will only be a few minutes. Sorry for the inconvenience, John From ibrahim at Stanford.EDU Wed Jan 31 09:48:26 2001 From: ibrahim at Stanford.EDU (Nabeel Robert Ibrahim) Date: Wed, 31 Jan 2001 09:48:26 -0800 (PST) Subject: EE410 schedule Message-ID: <200101311748.f0VHmQT04671@saga6.Stanford.EDU> To alleviate any potential conflicts between labusers and EE410, I was asked to provide a schedule of which equipment we'll be using. There are three sections of EE410: Weds. 1-5pm, Thurs. 8am-noon, Thurs. 1-5pm. Each section uses the same equipment and does the same processing. Here is the schedule for the rest of the quarter: Jan 31, Feb 1 ------------- svgcoat ultratech svgdev drytek2 Feb 7, 8 -------- wbsilicide tylanbpsg tylan7 Feb 14, 15 ---------- amtetcher drytek2 matrix wbsilicide gryphon Feb 21, 22 ---------- wbmetal drytek2 wbmetal tylanfga