jaclaz

Of course you are sure that the password is correct, aren't you? I don't think there has been any change in the encryotion between the two versions, is it possible that the file is somehow corrupted? You can have a try with openoffice.org, it can open Excel 2003 password allright: http://documentation.openoffice.org/online...protection.html You might want to use a "Portable build": http://portableapps.com/apps/office/openoffice_portable So that you don't need installing it to try it. jaclaz

Just as an appendix to my previous post about the problems with the NT/2K/XP floppy driver, I recently found this nice thingie: http://alter.org.ua/en/soft/win/floppy/ an alternate Floppy Disk driver that allows for the 1.76 Mb format. jaclaz

First result in Google for "imagecfg": http://www.robpol86.com/Pages/imagecfg.php jaclaz

evanhoe, if you type D and press [Enter] key, you are telling DOS to execute the "D" command (which does not exist) if you type D: that's D followed by colon, and press the [ENTER] key, you are telling DOS to change to the D: drive. Drives in DOS are NOT A,B,C,D but rather A:, B:, C:, D: That's why I suggested you read a bit on the two links I gave you..... ...you see, to repair a car you need, besides reading a manual and listening to hints and tricks by friends, some basic knowledge, you'll have to know that screws (generally) tighten when turned clockwise, and you must be prepared to get your hands dirty... ...same things applies to PC's .... ...the alternative, of course, is to take the car (read PC) to the shop and exchange money for the knowledge you are missing... ...real problem comes when you are missing BOTH money and knowledge... jaclaz

Cytomax, are you aware of Murphy's Law? NO program, NO software, NO hardware can foresee the event of a break up. S.M.A.R.T only "looks" from time to time for some parameters, and if any is "strange", throws an alert. A perfectly sound (as seen by S.M.A.R.T. or ANY other technology) HD can fail a few milliseconds after the end of the scan. If you want to be safe, backup, if you value your data, backup, and yes, it has a cost. What you might be careful about would be the actual software and media you use to back-up. jaclaz

eidenk, do take a deep breath , and re-read the sentence. "It is not recommended" does not mean "impossible". It is perfectly possible to make up to 4 primary partitions on a disk, and if you use some particular MBR's you can even make MORE than 4 . The point is that a number of Operating Systems (particularly different versions of DOS and Win9x/ME) were developed and tested with the assumption that only one Primary Partitions in the MBR. Using these operating systems on multiple primary partitioned hard disks can lead, in particular occasions, to data corruption , unlless all partitions but one are "hidden" at boot time, that's the reason why it is "not recommended". Programmers of tools like the original MS FDISK evidently thought that to be so serious as to include in the tool a mechanism preventing the creation of more than one primary partition. Several other tools, including Freedos FDISK, do not have such a limitation. Please re-read this: http://www.msfn.org/board/index.php?showto...mp;#entry463153 and linked posts therein, where the matter is discussed. jaclaz

I guess you mean: Don't you? jaclaz

Well, it works for me. Search on google for "ABC Amber Lotus Converter" jaclaz

Why don't you use isolinux or grub4dos: http://www.911cd.net/forums//index.php?sho...c=18657&hl= jaclaz

You are failing to specify exactly how the machine is partitioned/which filesystem(s) you are using, also which bootloader are you using for mandriva (possibly GRUB?). The idea should be that you install Mandriva first, putting Grub in the MBR, then you install windows 98 (overwriting the MBR), then you boot from the linux CD restoring the Grub MBR, then again you add an entry in the Grub menu.lst for Win98. Another possible option can be using grub4dos (that can boot directly IO.SYS) but it shouldn't be needed if the partitioning is correct. Finally make yourself a bootable CD with DOS on it, or get this: http://ebcd.pcministry.com/ if your floppy doesn't work. jaclaz

If you are interested in this kind of apps, you can find some more similar ones here: http://www.911cd.net/forums//index.php?showtopic=16534 Particularly, nfgdump has full command line support and has some really nice features. jaclaz

It depends on the kind of application. Some will work allright once installed, some won't. For the first kind is a matter of "working around" the installer checks, for the second kind is either impossible (like missing .dll's, subsystem, whatever) or needing some "deep" modifying of the .exe. Check these: http://www.msfn.org/board/index.php?showtopic=94003&hl= http://www.msfn.org/board/index.php?showtopic=62418&hl= jaclaz

NOT free, but still affordable: http://www.processtext.com/abclotus.html jaclaz

Hmmm, http://www.msfn.org/board/index.php?showtopic=93422 jaclaz

Not much, basically because at the moment I won't touch Vista with anything but a 10 feet pole , but two things might interest you or other members: 1. BCD is a Registry hive: http://www.911cd.net/forums//index.php?showtopic=19439 2. Nuno Brito is working on a tool to read and write Registry hives: http://www.boot-land.net/forums/index.php?showtopic=1703 http://www.boot-land.net/forums/index.php?showtopic=1839 I am trying to put together in the first thread every reference I can find on Registry hives, if anyone has some more info/links, he is welcome to join us in the "game". jaclaz

As said, I have no idea about WHY it happens, all I can do is to suggest a procedure (HOW) it would be possible to (hopefully) track down the problem. Basically that conditional IF(ISERR(FUNCTION),0,(RESULT)) will show 0, possibly a blank cell if EXCEL is set not to show 0 values, WHATEVER error the FUNCTION actually gives as result. Such an error can be derived by a number of causes, knowing the type of error might help. It is possible that the problem is due to some differences in the general settings of XL2003 when compared to XL2002, something in Calculation Tab, maybe. jaclaz

Evanhoe, sorry, but you seem like missing (no offence intended ) some basic knowledge, you will need to re-read the given link: http://www.uninets.net/~blaisdel/WindowsExtractCom.htm and also learn some basic DOS commands, here are a couple good start pages to get the hang of it: http://www.users.globalnet.co.uk/~jchap/tvdt.htm http://tnd.com/camosun/elex130/dostutor1.html You need to find WHICH .cab files has User.exe (and other missing/corrupted files) inside. (sorry if I cannot give you the exact location, but files inside .cab files are organized differently according to Win9x edition and language version) Boot from the floppy. Type MD C:\cabtemp [ENTER] this makes a temporary directory on your C: drive Now issue: D: [ENTER] Dir /S *.cab >C:\cabtemp\cabdir.txt[ENTER] this makes a .txt file with the list of all .cab files on the CD Rom Now issue: A: [ENTER] Edit C:\cabtemp\cabdir.txt [ENTER] you will be able to see in which directory (probably \Win98) the .cab files are Exit the DOS editor and type extract /a d:\Win9x\Win98_21.cab user.exe /l C:\cabtemp\ [ENTER] substitute in the above "Win9x" with the actual Directory name where the .cab files are. if the file is not found, repeat the above substituting Win98_21.cab with: PRECOPY1.CAB mini.cab BASE4.CAB CATALOG3.CAB DRIVER11.CAB NET7.CAB PRECOPY1.CAB i.e. with the first of each similarly named .cab files. Loop through the above until you extract into C:\cabtemp directory all files you need. The you need to copy the newly extracted files onto your (possibly corrupted) ones, overwriting them, most probably they are in C:\Windows or C:\Windows\System, to make sure issue C: [ENTER] dir /s user.exe [ENTER] loop into the above with all file names and jolt down where they are, then issue: Copy /b C:\cabtemp\filename.ext C:\Windows [ENTER] substituting each time "filename.ext" with the appropriate filename and "C:\Windows" with the appropriate directory jaclaz

GREAT find! jaclaz

Yes, it is possible, the method using WINNT.EXE is fully tested and functional, start here: http://www.msfn.org/board/index.php?showtopic=92644 and follow given links jaclaz P.S.: just for the record what you call "fixing a computer" appears to me, according to what you say rather a "re-formatting and re-installing"...

It is also possible that there is some mixups in the Registry. Though I think it should show in Disk Management as well. You can try (won't make any harm even if it does not work) this thingie here: http://www.uwe-sieber.de/usbdlm_e.html there are also some useful tips here: http://www.uwe-sieber.de/usbtrouble_e.html jaclaz

First thing I would do is to remove the IF(ISERR check, with that enabled, ANY error will return value 0, without it, it should show some error, like N/A or NAME?: change from to jaclaz

Am I? I guess that you really need to thank google (and my smart using of the word "booklet" as search term ) jaclaz

The function is available in newish versions of Word (2002/XP or 2003): http://thesource.ofallevil.com/education/createbooklet.mspx http://word.mvps.org/FAQs/Formatting/BookletPrinting.htm otherwise you need a few lines in VB Macro: http://word.mvps.org/FAQs/MacrosVBA/BookletMacro.htm http://www13.addr.com/~kenyonck/word/bookletprinting.htm or use the old method of "linked textboxes": http://support.microsoft.com/kb/120778/en-us jaclaz

I am not sure I got your problem correctly, but the "d:\" path should be the problem, usually Win9x install files are in a folder like "d:\Win9x\". As an alternative, you can use as said Extract.exe from DOS: http://www.uninets.net/~blaisdel/WindowsExtractCom.htm jaclaz

You can try manually, using extract.exe from DOS (no GUI) to replace the offending file(s), check this: http://support.microsoft.com/kb/192832/en-us and follow to: http://support.microsoft.com/kb/129605/EN-US/ About the enable.vxd problem: http://computing.net/windows95/wwwboard/messages2/533.html http://www.hftonline.com/forum/printthread.php?t=6786 http://www.geocities.com/Athens/Troy/6883/...l#Understanding VMM32.VXD Remember, Google is your friend.... jaclaz