Windows 98 Se Boot Disk Download

[Deandra Uleman]

Youcan create a bootable USB flash drive to use to deploy Windows Server Essentials. The first step is to prepare the USB flash drive by using DiskPart, which is a command-line utility. For information about DiskPart, see DiskPart Command-Line Options.

In the new command line window that opens, to determine the USB flash drive number or drive letter, at the command prompt, type list disk, and then click ENTER. The list disk command displays all the disks on the computer. Note the drive number or drive letter of the USB flash drive.

If your server platform supports Unified Extensible Firmware Interface (UEFI), you should format the USB flash drive as FAT32 rather than as NTFS. To format the partition as FAT32, type format fs=fat32 quick, and then click ENTER.

I am aware that the preferred approach is the use the Virtio device from the start and install the appropriate virtio driver when prompted. Unfortunately I was having some separate issues with changing the CD in KVM (I couldn't get 2 CDROM devices to work either).

Boot the VM, it will enter in safe mode. Booting into safe mode automatically enables and loads all boot-start drivers will be enabled and loaded, including virtio. Since there is now a miniport installed to use it, the kernel will now make it part of the drivers that are to be loaded on boot.

A fairly simple answer is provided - and may work in many cases, along with hints at other options. If (like me) you're not able to switch to IDE and forced to use VirtIO, then the following alternative approach might work:

If the last step is unfortunately required, one more difficulty that might beencountered is if the Windows boot CD cannot understand the VirtIO disk becausethese drivers were not included in it by Microsoft.In this case, one needs to create a custom boot CD/USB that containsthese drivers, but make sure that you start from a Windows ISO that isof the same level as the installation by getting the latest one (currently 1511).

It is unfortunately possible to have driver perfectly installed and STILL get "inaccessible boot Device." The reason is a bit shocking (I find): a Win 10 installation "remembers" the drivers that were required when it was first installed, and by default WILL NOT load other storage drivers at boot time. This is done, it seems, to "piracy" -- it makes it difficult to run the "same" installation on different hardware. There is some great documentation on this "feature" in this post from the gentoo forums. The essence is as follows:

The Drivers that are targeted for forbidden-to-load-at-boot can be determined as follows:Within the registry key Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services there is one subkey for every driver known to the installation. The name of this subkey is just the name of the driver. Within each driver subkey, there will be a subkey "STARTOVERRIDE" if that driver is to be prevented from loading at boot. In particular, within the STARTOVERRIDE subkey there is a parameter whose name is "0" . IF the value of this parameter is "3", it will not be loaded at boot time. Setting this value to 0 instead will 'override' behavior.

I myself just go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services and search for "STARTOVERRIDE". Each time i find it, if there is name under it called "0" with value "3", I change to "0". This seem to be overkill, you only need to change the drive that needs to load. In my case there are several of them, and I never remember which, so I just do an "F3-search" within that 'services' section.

And one final tip which isn't needed for current, signed, virtio storage, but might be to someone else reading this if they want to use a more experimental driver that is not (yet) signed: I found that EVEN after doing the above trick, I ALSO needed to boot into the advanced options screen and choose F7 ("disable driver signature verification"). Annoyingly, it wasn't enough to set the bcd flag to disable driver verification, because the driver needs to load before the machine reads the BCD and finds out that it doesn't need to verify the signature.

All in all, not Microsoft's most shining hour. You really have to hate your users if you'd rather give legit users a made-up artificial Blue-Screen than allow people to (say) replace a SATA disk with an NVMe disk and have it "just work."

I want to convert to Dynamic Disks and mirror the first drive to the second. Will Windows automatically adjust the EFI boot data in NVRAM to ensure that the OS can still boot? This prompt really makes me doubt if it can or not:

This message prompt is a bit unclear because it may scare you into thinking that your system is going to be non-bootable. The critical part of the message that really explains why you don't necessarily need to worry is the bit in parentheses: (except the current boot volume).

What Windows actually does is it intelligently updates your boot data as needed to accommodate the dynamic disks of the operating system that's currently running. So if you convert a disk from a basic to a dynamic disk, and the only OS you care about on that disk is the one that's running right now, Windows will not break its own boot in the process of converting to a dynamic disk (unless there's a bug in Windows). I suppose this is because Windows knows enough about its own boot sequence to update and fix it when converting from a basic to a dynamic disk.

I read in chat that another user has had success with this on a BIOS/MBR based installation. In my case, Windows must be installed to boot in UEFI mode on GPT formatted disks, because NVMe SSDs can't boot in legacy BIOS mode (the BIOS can't initialize the disks and hand them over to the bootloader).

So, regardless of whether you have a BIOS or UEFI based boot sequence, the expectation -- barring any really unusual setup or a Windows bug -- is that converting the currently running system disk to a dynamic disk does not break boot of that OS.

I'm need to find a method to programmatically determine which disk drive Windows is using to boot. In other words, I need a way from Windows to determine which drive the BIOS is using to boot the whole system.

p.s. Just reading the first sectors of the hard disk isn't reveling anything. On my dev box I have two hard disks, and when I look at the contents of the first couple of sectors on either of the hard disks I have a standard boiler plate MBR.

Edit to clarify a few things.The way I want to identify the device is with a string which will identify a physical disk drive (as opposed to a logical disk drive). Physical disk drives are of the form "\\.\PHYSICALDRIVEx" where x is a number. On the other hand, a logical drive is identified by a string of the form, "\\.\x" where x is a drive letter.

Edit to discuss a few of the ideas that were thrown out.Knowing which logical volume Windows used to boot doesn't help me here. Here is the reason. Assume that C: is using a mirrored RAID setup. Now, that means we have at least two physical drives. Now, I get the mapping from Logical Drive to Physical Drive and I discover that there are two physical drives used by that volume. Which one did Windows use to boot? Of course, this is assuming that the physical drive Windows used to boot is the same physical drive that contains the MBR.

You can use WMI to figure this out. The Win32_BootConfiguration class will tell you both the logical drive and the physical device from which Windows boots. Specifically, the Caption property will tell you which device you're booting from.

2 and 3 should be easy to find - I'm not so sure about 1. Though you can raw disk read to find an MBR, that doesn't mean it's the BIOS boot device this time or even next time (you could have multiple disks with MBRs).

You really can't even be sure that the PC was started from a hard drive - it's perfectly possible to boot Windows from a floppy. In that case, both 1 and 2 would technically be a floppy disk, though 3 would remain C:\Windows.

On Windows 10.Open "Computer Management"Look for "Storage" in list "left top side of page"select "Disk Management"On section of page showing the list of disks and the partitions find the disk that has the partition assigned as drive C:On that disk containing C: partitionUse the right mouse button to select the Square section containing The Disk Number, Type of drive and size in GB . When menu opens select the Properties.A window will open showing what drive hardware was used.

We offer a boot disk for everything from MS-DOS 3.3 to Windows XP Professional. These disks can be used to setup a new hard drive, scan an existing hard drive for errors, install or re-install Windows, upgrade your PC's BIOS, run DOS utilities, vintage DOS games and much more.

I have an IBM 466 DX2 with the default CD-ROM drive installed like normal. I wanted to install Windows 95, so I first tried to install on top of the version of DOS already on the hard drive. It had the driver for the CD-ROM installed and booted into setup. Partway through setup, it detected a previous version of Windows on the hard drive, and said that I needed to get a Windows 95 upgrade. Of course, I wasn't going to find that, so I had DOS format the hard drive. I then tried to do a install with the boot floppy. When booted, it displays an Oak Technologies CD-ROM driver, but then says it doesn't find a CD-ROM drive and aborts. I need to find a driver that works with the Windows 95 boot disk so I can boot into setup.

From your pictures you have a CD-ROM manufactured by Matsushita for IBM with a model number of CR-563BBZ. This drive uses Matsushita's proprietary interface, so won't work with the the OAKCDROM.SYS driver which only supports CD-ROM drives using the IDE interface. It is however not connected to your sound card, its connected to it's own LaserMate CD-ROM interface card (labelled LMEP0084C). Your sound card is just behind it, it's the card with the silk screened CT2770 at the top.

I'm not sure if your LaserMate interface card needs its own drivers, or if it's compatible with the Matsushita interface card and so can use the Matsushita drivers. If it is compatible then what you need to do is copy CDMKE.SYS to the root directory of your boot floppy. You'll then need to add the following line to your CONFIG.SYS file:

3a8082e126