dencorso

JavaScript and JAVA are not the same thing.

Also read posts #1, 11 and 12 of theis thread: http://www.boot-land.net/forums/index.php?showtopic=8307. HTH

Here: Windows 98 USB Mass Storage Device Drivers. Got to the Win 98SE section. They have NUSB24e and other old versions, besides the current NUSB, in various languages.

No. You've got me wrong. In my machine, WinImage can transfer all but DOS 1.xx images to all odd-formats of floppies, provided I don't use it to actually format. That is to say, the "Write disk" works all right. Whenever I try to use either "Format and write disk" or "Format disk" with formats of 720 kB or less I also get an "Error. Disk error on track x, head y. Floppy Error". With the standard formats it works also for formatting and sometimes it is able to format a 3.5" floppy to 1.2 MB. FDFormat, in true DOS, is my preferred way to do all formatting. When it fails, the floppy actually is bad. But I bet there is yet another utility that may transfer the images in your machine: DiskImage. Did you give it a try?

NUSB27e ? That one I wasn't aware of! Are you sure you didn't mean NUSB24e ? BTW, I'm glad to see you around again, Drugwash!

Try "g:\minint\setupldr.bin".

Welcome to MSFN, heppener! I'm sure you just found the right place for all things unattended!

Welcome to MSFN, liquidzgurl! I see you've been very active since you joined. It's good to have new people who contributes, instead of just lurking in the shadows. Nice to have you around!

*** WARNING: THIS IS NOT FOR THE FAINT OF HEART!!! *** IT CAN MESS UP ONE'S PARTITIONS BEYOND BOOTABILITY, AND IT CAN CAUSE IRREPARABLE DATA LOSS, IF ONE REPARTITIONS OR FORMATS THE WRONG HDD BY MISTAKE. Well, using NUSB 3.3 as the driver, and having the care to copy any file to the media with Windows Explorer before proceeding, to get it fully mapped (this is necessary!), you can then, on a Windows DOS Box, partition and format them as desired, using the The Ranish Partition Manager version 2.43 (beta) a.k.a. part243, just ignore the warning about not working under windows, and take care not to mess with any of your HDDs, which will *usually* be listed before the flash media. Then stop and remove the media. Dismiss the DOS box. Then reinsert and again copy any file to the media with Windows Explorer before proceeding, to get it fully mapped. Go back to RPM, in a new DOS box, and verify it's all right, but change nothing. If it doesn't seem right, stop and remove the media again. Dismiss the DOS box again. Then reinsert and again copy any file to the media with Windows Explorer before proceeding, to get it fully mapped. This time, in yet another new DOS box, RPM will show exactly what you had done, and you'll quit it without changing anything, once again. You may now delete the files you copied to the media just to have it mapped as a HDD. Now, in the same DOS Box, sys the media, and it should be bootable in DOS, all right. I usually also set the volume label with the label command, just after transferring the system to it. This is my preferred method for rendering bootable any kind of flash media (it works with SDHC cards and with pen-drives). Once you learn how to do it, it's quite fast to be done. But due care must be used to avoid problems. Read carefully the above instructions and only proceed if you are 100% sure you know what you're doing. These instructions do work, but a single small mistake can and will cripple your system!!! If your system stops booting, you have only yourself to blame. You have been warned!

That pop-up is caused by the last update AVG released, before dropping support to 7.5! It drove me nuts, too! What I then did was to deploy my full system backup image, obtained 5 days before, so that I rolled back to a previous update state, before the nagging was added. And disable AVG's automatic updates. I'm positive its caused by the last update available. But I still didn't find a way to roll back just AVG's update. Sorry! There must be one, though.

I confirm it. It's now working OK in IE, too. Congratulations, xper, you fixed it! And thanks a whole lot! It's broken again! At least on IE.

Welcome, Dr. Vista! I'm sure you'll find lots of interesting things here.

It's been a long time now since this question was posted and got no reply. I decided to resurrect it in the hopes someone has found a solution on how to integrate network ability to WinRE. So... Is the dream of a WinRE with websurfing ability still just a dream?

Congratulations for the successful data recovery, Multibooter! That's not easy at all! I'm happy to read IOSys98 did help. But I have a question for you, just for the record: Were you using also the VFAT.VxD official update (Q277628) or it was all done with the original VFAT.VxD?

Not yet...Open NUSB31 with WinRAR or 7zip and extract EXPLORER.EXE from inside it. Rename it to EXPLORER.31 and put it into c:\Windows. Reboot into true MS-DOS mode, and issue the following commands: C:<Enter> CD\<Enter> CD \WINDOWS<Enter> REN EXPLORER.EXE *.33<Enter> REN EXPLORER.31 *.EXE<Enter> <Ctrl><Alt><Del> And, after the machine is back to Win 98SE, check whether your issue is solved or not. Good luck.

Very true. And, since our most capable developers have their hands full already, for the present and into the foreseeable future, and since we're not exactly an exponentially growing community, I dare say no amount of pushing, and no amount of shoving also, BTW, will be capable of preventing this ideia from being on idefinite hold for the present, the near future and even maybe the far future. While more ideas are always welcome, more developers willing to work on 9x/ME are much more welcome, but I sincerely fail to see an enormous horde of developers in the horizon, brawling furiosly in order to ascertain who'll be the first to start new projects in 9x/ME...

Welcome to MSFN, AquaFire! Hope you enjoy your stay! Well, format it does! Now, however, "format", in this context, must mean something different from what it usually does, since the all the data remains there. To quote from the post before yours: So, then, it's opportune to repeat here my advice of some posts above: The only thing that has changed since then is that now there are actually 1848, not 1838, posts before yours... Read them slowly, bookmarking those that appear to be important or most interesting. Then, after you've worked your way through the whole thread, return to them and restudy them. And don't forget to do the same to the external link pointed in various posts along the thread. Some are quite illuminating.

Enough! @Leo Natan: You're hereby suspended for 3 days, to reflect upon your ways. Thread closed.

Try the following procedure: 1) Go to Control Panel -> Add or Remove Programs. 2) Remove the USB 2.0 drivers from there. 3) Reboot. 4) Instal again NUSB 3.3. 5) Reboot. 6) Test and report.

Since Marius '95 solved the VEN/DEV problem (thanks, Marius '95, you rock! I didn't know that program, either... ), here is the solution for the remaining VID/PID problem.

If I undestand you right, you've installed 3.1, then 3.2, then 3.3, when it finally went wrong... is that it?

There are 1838 posts before yours. Read them all patiently, and all will become clear to you. The price for not doing this is risking to fry your HDD for being in a haste. Take your time. Desperation only leads to failure. Easy does it.

Welcome onboard, bluesingincat! I'm sure you're gonna find many answers here to many of your problems with Vista, and probably, sooner than you can imagine, will be providing others with some answers, too!

None that I know of. But, by all means, clone the disk with Anadisk to a good floppy, while you still can, before using Anadisk more extensively to try to salvage something from the bad sectors. And do clean the heads of your drive before proceeding, and after you're finished with the bad floppy.

UNICODE and Win 9x/ME don't usually mix well together...