There are always many possible ways to mess up computer software. HPSWINFO is no exception. The best anyone can do is to follow the procedures to ensure that everything is done according to the directions, then double and triple check your work. Personally, I recommend keeping a log of each system and which patches (or other changes) were made on specific dates. I have recently been using Patch/iX or AUTINST for most of my installations, so excuse me if the following does not apply to Stage/iX or AUTOPAT... If you go through the patch procedure (either AutoInst, AutoPat, Patch/iX or Stage/iX) and you neglect to rerun the utility or do the RESTORE from the Custom SLT, then the correct HPSWINFO will not be restored. The information about the most recently installed patches will not be reflected in HPSWINFO. Furthermore, other even more critical files were probably not restored and you have a nightmare mis-matched system. The other mis-match has already been meantioned. An update from a mismatch SLT possibly using the NOCONFIG, will certainly confuse the issue. HPSWINFO is not a culprit. It is not a final authority. It is simply a file. It can be easily be corrupted. Mark Ranft - HP e3000 Internet Consultant Pro 3K www.Pro3K.com [log in to unmask] (612) 701-8182