jaclaz

Well, I simply thought that a Driver is a Driver and a Tech is a Tech, and "coupled" "employee#" with Designation. You can simply overwrite the formulas in colums "Designations" and write the Designation manually or choose it from a list. jaclaz

See if Vlookup2.xls (actually based on "requirements.xls") suites you. jaclaz Vlookup2.zip

Which means you completely failed to read what I wrote AND the given link. title boot xp find --set-root /minint/SETUPLDR.BIN chainloader /minint/SETUPLDR.BIN The build must be in directory: ROOT\I386\ or ROOT\minint\ i.e.: G:\minint\ in your case of a HD, or you need to hexedit the SETUPLDR.BIN jaclaz

.xlsx? .docx? Bad, bad formats. Can I have them in plain .xls and .doc? jaclaz

See if this (unrelated) puts you up on a path leading to a solution: http://www.msfn.org/board/excel-2007-compl...la-t137511.html jaclaz

Make a "static" Data_Area on a sheet (that you WON'T sort) And use VLOOKUP. Or I am not getting what you are wishing to do? Can you explain what is that you are willing to do/need (as opposed to how you are doing it and it is not working)? jaclaz

You CANNOT have /PE/I386/. If on CD/superfloppy the hardcoded path is: /I386/ if on HD or hard disk like device (USB stick partitioned), path is: /minint/ Read this too : http://www.911cd.net/forums//index.php?showtopic=17504 jaclaz

Sure , IF he has cable internet, IF he uses a network connected router to access the Internet. But wait, all network connected internet routers I have seen have more than one port, usually at least 4, so there won't be the problem at all for two PC's. We must be living on different planets. You are accustomed to far "newer" or "high end" hardware. However, just for the record, a Lan card can have more than one IP address: http://www.itsyourip.com/networking/how-to...ows-2000xp2003/ http://www.metacafe.com/watch/331275/multi...k_card_windows/ jaclaz

If I may, I doubt that a member asking about a website builder has the experience/knowledge to know what a CMS is. Just in case: http://en.wikipedia.org/wiki/Content_management_system http://en.wikipedia.org/wiki/Web_content_management_system jaclaz

Actually I suggested a USB stick, or flash drive or pen drive, you can use an old 32 or 64 Mb one, if you can still find one, or buy a 512 Mb or 1 Gb one for a few bucks. The PXE way is absolutely valid , though setting up a PXE/TFTP server and troubleshooting it may prove to be a looong path to take. jaclaz

Your crystal ball is working much better than mine. What I saw was a guy with a (parallel only) printer and a (USB only) scanner, a laptop and a desktop (and maybe, but it was really out of focus, a USB connected ADSL Router). For the record, it is the first time in my life I hear that you need to "undo" static IP to connect to the internet. Please don't tell it to the several SOHO lans I put up for friends, that all have static IP's and, probably not knowing it won't work, are happily connected on the internet. Also, I've never seen a router capable of connecting 255 PC's for sale at around 40 bucks...., I have seen a few hubs with max 8 ports for that money. jaclaz

I don't think it will work, actually never tried. But why not making a Recovery Console on USB stick? JFYY: http://www.boot-land.net/forums/?showtopic=2254 http://www.boot-land.net/forums/index.php?showtopic=8785 Easiest would be following this advice: http://www.boot-land.net/forums/index.php?...c=8785&st=6 jaclaz

NO. I am notoriously cheap, so get the cheapest HD you can find and the cheapest external box or adapter. (or the cheapest combo) I mean, all Hard disk manufacturers are on the market, and they are in competition, their products are very similar, this time Seagate had an hiccup, next time it could be another maker. Since this is going to be a backup drive, you don't need "top speed" nor "huge cache", and same things goes for the USB or eSATA or whatever converter/adapter/external case. If you avoid Seagate, the only "good" thing you do is to (fractionally) show them how they behaved "bad" in this occasion. jaclaz

Sure it can, that's the "normal" behaviour of any "just powered up" drive, though I would call it more "purring", besides not reading all the posts, put also some ears protectors on, and boot the PC with the drive connected, can the BIOS detect it? If yes, you have NOT the BSY. If no, you probably have the BSY. If you have a "real" clicking sound, it may be something else, but if you go back a little: http://www.msfn.org/board/index.php?showto...mp;#entry881140 you will find that user Greenie17, after some initial misunderstandings: http://www.msfn.org/board/index.php?s=&amp...st&p=881318 http://www.msfn.org/board/index.php?s=&amp...st&p=882303 Succeeded: http://www.msfn.org/board/index.php?act=fi...&pid=882373 About the DKU-5 or whatever other Nokia/telephone cable, there are two schools of thoughts: some people (and myself) think that one is ALREADY risking a bit too much in doing this and that adding in the recipe a "non-standard" cable/converter is an additional risk, and that recommend "proper", documented interfaces some people think (and have had various degrees of success) that using the "non-standard" cables is OK a few people (who can afford it or that have invaluable data lost) think that we are all a bunch of crazy guys and that the only way out is a professional service A few pages back there is a COMPLETE review of the various "Nokia" cables: http://www.msfn.org/board/index.php?showto...807&st=1756 Once you have determined whether you have probably a BSY or not, do as dencorso suggested and start reading the whole thread. AND these ones: http://sites.google.com/site/seagatefix/ http://www.mapleleafmountain.com/seagatebrick.html jaclaz

Forget (for the moment) the 1848 posts. Read FIRST post ONLY. These lines ONLY (lines #6, #7 and #8 of FIRST post: Now, WHICH is the difficult part? You NEED to hook the drive directly to the motherboard to check how BIOS sees it (or fails to). If it sees it, but with 0 size, it's 0 LBA, if it cannot see it is EITHER: a defective cable a defective connector a defective PCB of the drive a defective controller on the motherboard OR a BSY If you checked: the cable the connectors (with a multimeter for obvious ) the PCB of the drive (no, I am joking , you cannot test this, let's assume you did and it's functional ) the motherboard controller (with an other disk) and everything was well, THEN it's a BSY error. jaclaz

Upgrading firmware should theoretically be a "data safe" procedure. (just imagine, if it was not, the amount of lawsuits against HD manufacturers) BUT even if the risk of a data loss is remote, Murphy's Law ALWAYS applies. Imagine what could happen if any of the following happens WHILE you are upgrading: a mains surge a black-out any number of casual events, including the controller on your board "acting strange" or your cat playing with the cables and what if any of the above happen AFTER you have updated the firmware and you lose all that data? Better be safe than sorry, if you fixed your brick, you already were lucky enough, apart from this specific Seagate problem, having one single copy of anything on a single hard disk is asking for troubles, you should always have AT LEAST two copies of ANYTHING valuable on AT LEAST two different media/devices. jaclaz

I know. It was a rhetorical question. Well, though I do not agree with the "pushing" idea, and with the way it is done, I personally find that the "plot" is not wrong in itself, only I find that it would be nice to have Open Source alternatives for Windows 9x/Me components that give you more features, while I find useless alternatives with SAME features. As an example, if that library (or more accurately IFS drivers deriving from it) would allow access to NTFS and exFAT64, it would be useful and could replace the "standard" MS ones ALSO for the functions that we already have. And however, having a library, while being a good thing, is far from having an actual working driver. jaclaz

Thread Pinned (Sticky). jaclaz

I don't know. What would be the use of a FAT12/16/32 library on systems that already support those filesystems natively? jaclaz

If I may, you are doing it more difficult than needed. See if this thread helps: http://www.msfn.org/board/index.php?showtopic=127593 Basically: Get dos image Mount it under 2k/Xp/vista Add the BIOS flashing files burn a CD with El_torito floppy emulation jaclaz

Alternative: DIY job: http://www.msfn.org/board/index.php?showtopic=128807 http://www.msfn.org/board/index.php?showtopic=133387&hl= jaclaz

I doubt there is anything you can do. If a sector is bad, it is bad, if only a few sectors are bad and this prevents reading a bigger chunk of otherwise good sectors, you have some probabilities. You can try a "file based" recovery, PHOTOREC: http://www.cgsecurity.org/wiki/PhotoRec Or a sector based DD: http://www.boot-land.net/forums/index.php?...ic=7783&hl= the latter has more chances, due to it's interesting approach, but still don't expect a miracle. jaclaz

Things to read, that may be of use: http://www.911cd.net/forums//index.php?showtopic=21231 http://www.911cd.net/forums//index.php?showtopic=22975 There is an utility around that can change the UDMA support of the card and as well "flip" the "Removable" bit. Whether this solution: helps can be applied to the particular brand/make/model of card is for you to find out. (Your mileage may greatly vary ) jaclaz

Modified paragraph C4 of the first post to include this advice. To be picky not entirely accurate. If you only FORMAT the MBR won't be touched at all. If you FORMAT from Win9x (please read DOS) the PBR of the FORMATted partition will be replaced by the Win9x/DOS one, invoking IO.SYS and MSDOS.SYS. If you FORMAT first active primary partition of first disk you will also need to copy back to it the boot files, typically: DOS/Win9x: IO.SYS MSDOS.SYS COMMAND.COM NT/2K/XP/2003: NTLDR NTDETECT.COM BOOT.INI Vista/2008/7: BOOTMGR \boot\BCD And, if needed use BOOTPART to fix/repair the bootsector or PBR. In other words, FDISK changes the MBR, FORMAT changes the PBR. jaclaz

Here: http://www.msfn.org/board/index.php?showforum=157 jaclaz