rloew

Yes, it is very possible, I am usually very accurate and punctilious . One so far. Reduce that by the fact that Reading about something doesn't guarantee purchase. Still leaves N<1700*X You share some common trait with one of the greatest geniuses in the whole history of mathematics, Pierre de Fermat : That's called "Closed-Source". Also, have you ever heard of a "pre-marketing survey"?

And I suppose you are going to read all 1700 of them. Would anyone else? If so, raise your mouse. I downloaded your attachment. The headers appear to be padded for a specific CD configuration, it would not support Joliet, for example, and do not include even a null ISO block. I already have a single tool that can take a Floppy Boot Image, like the one Dencorso posted, along with one or more folders of Files for the rest of the CD/DVD, and burn them in one step. The other tools I mentioned previously were to facilitate making the Floppy Boot Image.

I don't disagree. I take my drivers where I can find them. But it makes that particular Motherboard a lot less "special".

Rjecina is correct: this motherboard using nForce3 250 chipset and you can find drivers for it (on Nvidia webpage or other place). Older version of HT would have a rather small impact on overall performance. Btw, Rjecina, ALiveDual-eSATA2 is IMHO even better because of the presence of PCI-E slot (also 2 x SATAII/ 1 x eSATAII connectors). It depends on your definition of "official". Chipset manufacturers often refer you to the Motherboard Company's website for official drivers, as decisions make by the Motherboard manufacturer or BIOS developer can affect the requirements for a Driver.

My remark was more a "generic" one, you have something in your closet, you may be willing to sell it, but until you don't take it out of the closet and put it on display on your desk, under a big "for sale" sign you have 100% possibilities (read as "certainty") that noone will ever buy it, or the other way round 0% probabilities of ever selling it. Once you have it in plain view on the desk it is possible that someone is interested to it, you will have n% probabilities that someone will buy it, and no matter how little n will be it will always verify the n>=0 condition, with a chance of also verifying the n>0 one. jaclaz I could write a Program that turns the background to pink. Would it even be worth investing in a "for sale" sign considering that I have never seen anyone show an interest in a pink background. How do I know that N>X where X is the cost of the "for sale" sign. I have over 1700 Programs. Putting them on my Desk would cause the Desk to collapse under the weight of the "for sale" signs. The same would be true of my Website. This thread is the only one I have seen indicating an interest in extended Bootable CD Floppy Emulation, so this is the only "desk" worth putting it on. Incidentally: Doesn't help raise the value of N. @dencorso: Your latest Image is not totally empty but it should work. I would have worded it differently.

I just went to the Asrock Website. They do not list any drivers for Windows 9X. They start at Windows 2000. If you have Drivers for it, they are no longer official. Unless you have the 98SE Version of the RAID Driver, my Patch will still be needed for SATA. The Specifications say it is for AM2/AM2+ not AM3. It will tolerate AM3, but with reduced performance.

Depending on your configuration, you may need both. My Patch does not support the 7900GT by itself, it is not a Driver. You still need the free drivers. My Patch solves certain memory issues that can be aggravated by using newer Graphics cards.

My intention was that those "it"s should mean "your software utilities", not Nero nor UltraISO. But "it" is too vague. Sorry, my bad. The answer to your intended question is yes. My utilities allow you to specify the Emulation Type Code, including No Emulation, overriding the default based on the size of the Boot Image chosen. The only requirement is that the Boot Image be a multiple of 512 Bytes.

Nobody, me included. I said I looked (after all I have both installed) and neither Nero 6.6 nor UltraISO 9.36 (the latest) do, AFAI can see. I was referring to the "you" in "(as you said it does)" in your earlier post.

Sounds like excessive Resource usage rather than a Memory leak. Default Fonts are a sign of Resource depletion. Try using the Resource Monitor instead of a Memory Monitor to confirm it.

Who said Nero supports non-standard bootable ISOs?

I know,but I still don't find worth paying for an OS old like that.Unfortunately my motherboard does not have any compatibility mode option in BIOS. You get what you pay for. The Compatibility Mode is in Windows not the BIOS. You can either go into Safe Mode and set it, or you can go into DOS and rename the ESDI_506.PDR file in WINDOWS\SYSTEM\IOSUBSYS. You have to prevent the USB drivers from being installed, at least for the Port you are booting from. I have USB keys with bootable Windows 98, 98SE and ME on them.

I developed the utilities years ago. This thread is 4 days old. This is the first I have seen any interest beyond the standard bootable CD floppy emulation that can be handled with existing tools. Are the complete set of utilities (and instructions) to create such a .iso available or not? Or are they available only for sale? The utilities are complete. Some are already on my Website. I would need to write instructions for the rest. Is there any interest in them, to justify packaging them? Or are you just interested in a probably rather tedious workaround.

You and me both. I had purchased a copy of Half-Life 2, and not knowing about their plans I hadn't attempted to install it until after that deadline had passed. Needless to say I was extremely angry to find that I couldn't install the software that I had purchased under the assumption that it was designed to run in Windows 98. So from that day forward, I refused to install Steam on any machine or purchase/use any game that required it. I have yet to play Half-Life 2. (I know there are "workarounds" - I've just been too irritated to even care about trying them.) i'm not sure what the workarounds are. The only one I have heard of is KernelEx. I bypassed the "Unsupported Operating System" check, but it still failed and some of the DLLs are linked to NT only System APIs as well. I installed Steam from scratch, but it could not update and it doesn't allow offline useage. Offline usage appears to require validation at least once.

A quick question/observation... that has the potential to make this get off topic AGAIN... Do your/can your CD/DVD utilities work with Blu-Ray images/devices? I know Multibooter was having burn-quality issues during his tests, of course it is still unknown whether it was due to software, hardware, or media quality... In the event it is software related, your solutions might end up being the only "quality" Blu-Ray burning application available for Windows 9x... I only set up a Blu-Ray Drive recently so I have not added the necessary code for burning Blu-Ray disks. My builder code does not currently support UDF as it was designed for Data rather than Video so that may be another issue if not just burning images.

You can always create a smaller Partition than the Device size, or use a Hard Disk Partition for proof of concept. Non-Bootable Partitions can be as much as 256MB without Patching DOS, although some utilities don't work. The NT Boot Sector may be modifiable to support FAT12 but I suspect that NTLDR will not work

It would be a start, to find a way to reproduce the three .iso's easily (with a populated image). If you could create three .iso's with the given superfloppy sizes and freedos it would be perfect. If you check the given before link: http://reboot.pro/9916/page__st__28 you will see that using the simple, alternate approach, and as long as we want to only populate the superfloppy image, we can simply use the "header" of the .iso file in conjunction with a "populated image". The "rest of the CD" we will find later a way to populate, if we can reproduce the "header" with mkisofs + (if needed) a few hex edits via batch, rest of the CD should be a "piece of cake" . jaclaz For me, populating the Boot Image and the rest of the CD is the major part of the task. Extraction and Burning are straightforward. There is no particular reason to make three different sizes as Type 0x03 can handle anything from 36KiB to 36MiB. I usually create an Image appropriate for the amount of actual data I need on the Bootable Part and process it accordingly. Without custom scripts, Freedos is not going to do anything once it is loaded. You might as well just stick in a Floppy. Creating a "header" that includes the El Torito Header will require a number of Patches if you start Populating the rest of the CD/DVD. I could do it. Maybe you could do it. How many others do you think could do it. A Program would need to be written to automate the Process. Sounds like an awful lot of work to avoid buying my tools.

Steam did work on Windows 98 until 2007. It can still be used if you run offline. I didn't know about their plans so I went online after the deadline. They updated my Software and it no longer runs. If anyone still has the older version running, I would be interested in the core files that were updated.

On some of the newest Motherboards, some of the SATA issues seem to have propagated to the PATA firmware. I had to update my SATA Patch to include PATA drives. When my new Computer froze during Windows Bootup with the Drive Light on solid, I verified it was stuck initializing the Hard Drives. I rewrote my Patches to make it work properly. I never waited half an hour to see if the would ever boot. It could be timing out one sector at a time until it finally loads Windows. Windows 98 is "old" but my Patches are not. Your only alternative is to run in compatibility mode, which will be slow but not take half an hour. Booting Windows 98 from a USB Drive requires special handling, otherwise the USB Driver steals the Drive from the System and it crashes.

Sure they do not, as the DOS and Windows we are currently using were all made AFTER the "invention" of types 04, 06 and 0C, this is IMHO the same "side effect" as the "large Sectors vs. Small Sectors". If you try: DOS <3.3 DOS 3.3 DOS 4.0 DOS <=6.22 DOS >= 7.0 on a set of 01/04/06/0C partitions, your mileage should (and will) vary I think that in common language we could consider: FAT12 an ancestor of FAT16 FAT16 04 a sub-set of FAT 06 FAT 16 06 a sub-set of FAT 0C Then draw a line around 1995 and say that everything coded after is accessing *any* of the above in the same way (which allows for some of the tricks we are discussing). As I see it, trying dencorso'S image in DOS 3.3 should fail, as that version of Dos should know nothing about "Large sectors". jaclaz Of course I was referring to the later DOS Versions. The early ones had many limitations. DOS 3.3 would be limited to 32MB. Superfloppies and CD Floppy Emulations do not use Partition Codes, so that issue does not apply. The Partition Type for the LBA version of FAT16 is 0x0E not 0x0C. Type 0x0C is the LBA Version of FAT32.

After crashing Nero with some very long Directories, I wrote my own set of CD Writers / ISO Builders. Adding El Torito support was simple. A manual option lets me force Type 0x03 rather than 0x04 for the Boot Image when using Images between 2.88MB and 36MB. I see. Is this app (or set of apps) available? If yes, can you post a link to it? Or is it for "private use"? If yes, can you attach a couple of generated (empty, or with a few redistributable files in them) .iso's? RFDISK and RFORMAT are already on my Website. These are used to Create and Populate the Bootable Image. Partition Imagers are everywhere. I didn't Package my CD/DVD Utilities for sale as I had not seen any particular interest in their added features. People seemed happy with what they have. I'm not sure what the value of an Empty ISO is. It will just attempt to boot an empty Partition and fail. You still need to populate the Bootable Image and probably the rest of the CD as well. In any case dencorso is well on the way to creating one. @dencorso: Bootable Floppy Images need to be FAT12. Otherwise your new Image is fine.

Autoallocation only delayed the crash. Fixed allocation XMS RAMDisks usually cripple Windows immediately if they are more than a few hundred Megabytes is size. You will need a Non-XMS RAMDisk if you want to use more space.

DOS and Windows do not seem to care what the Partition Type Code is, if in the allowed range, when determining Filesystem Type. .

After crashing Nero with some very long Directories, I wrote my own set of CD Writers / ISO Builders. Adding El Torito support was simple. A manual option lets me force Type 0x03 rather than 0x04 for the Boot Image when using Images between 2.88MB and 36MB.

I don't want to be a nuisance (or not more than usual ) but could you share: the EXACT size in bytes of those? an example mkisofs command line to build such a super-floppy .iso? (or some reference to the above if available) 0x03: 1024*2*36 * 512 = 37,748,736 0x02: 1024*2*18 * 512 = 18,874,368 0x01: 1024*2*15 * 512 = 15,728,640 I have never used mkisofs, so I have no idea what it's syntax is.