Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
On 3/6/2020 1:51 PM, Jen via Freedos-user wrote: I tried this ↑ first – used GParted again to either rule it out or not as the issue, resized my C: partition (flagged as bootable) to 2GB, formatted it as FAT16 [*This time it put 1.99 MiB unallocated ahead of it*], I have a hunch that this is the basic source of your problem. That "nothing but blinking cursor" symptom is most certainly due to the fact that the MBR can't find the actual boot partition. I think there are some implicit assumption in there as to where the partition starts. Ralf -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
On Friday, March 6, 2020, 8:12:43 p.m. EST, Louis Santillan wrote: > “A screenshot of your boot options screen would be useful too.” http://jen-lik.es/bootm @Louis Santillan: My response to your other question is awaiting moderator approval because it was too long and exceeded 40KB., but it started by explaining: “I resized the partition to 2GB (and resized/moved all the ones after it) as one of the steps I took to try and fix the problem, decided to leave it that way. …” ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
Let me clarify... I don’t recommend running ZAPMBR.BAT on a multi-boot or multi-drive system. But, it doesn’t do anything you can’t do manually... Depending on a couple things. Try telling sys to update both the system files and the boot sector... sys a: c: /BOTH Also, fdisk has some MBR specific options. Like... fdisk /MBR 1 Ether should force new boot code to the boot sector. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
A screenshot of your boot options screen would be useful too. On Fri, Mar 6, 2020 at 5:04 PM Louis Santillan wrote: > All those files look good. Seems odd that you have 1.6GB free on the C: > drive of 7.8GB. A full install of FreeDOS with source is probably only 1GB > or so. > > What’s the content of autoexec.bat, fdconfig.sys, gem.bat, device.raw, and > shell.raw? > > On Fri, Mar 6, 2020 at 4:06 PM Jen via Freedos-user < > freedos-user@lists.sourceforge.net> wrote: > >> On Friday, March 6, 2020, 05:20:05 p.m. EST, Louis Santillan < >> lpsan...@gmail.com> wrote: >> > … “what does the following” >> > … “‘D:\> dir C:\*.* /w’” >> > … “return?” >> >> … >> [FDOS]·[GEMAPPS]···AUTOEXEC.BAT···COMMAND.COM···DEVICE.RAW >> FDCONFIG.SYS···GEM.BAT·KERNEL.SYS·NIC.TXT···SETUP.BAT >> SHELL.RAW···9 file(s)·252,897 bytes >> ·2 dir(s)···1,601,994,752 bytes free >> >> (^ w/o the dots, obviously) >> ‘SCREENSHOT’ [photo]: http://jen-lik.es/dirCw >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
All those files look good. Seems odd that you have 1.6GB free on the C: drive of 7.8GB. A full install of FreeDOS with source is probably only 1GB or so. What’s the content of autoexec.bat, fdconfig.sys, gem.bat, device.raw, and shell.raw? On Fri, Mar 6, 2020 at 4:06 PM Jen via Freedos-user < freedos-user@lists.sourceforge.net> wrote: > On Friday, March 6, 2020, 05:20:05 p.m. EST, Louis Santillan < > lpsan...@gmail.com> wrote: > > … “what does the following” > > … “‘D:\> dir C:\*.* /w’” > > … “return?” > > … > [FDOS]·[GEMAPPS]···AUTOEXEC.BAT···COMMAND.COM···DEVICE.RAW > FDCONFIG.SYS···GEM.BAT·KERNEL.SYS·NIC.TXT···SETUP.BAT > SHELL.RAW···9 file(s)·252,897 bytes > ·2 dir(s)···1,601,994,752 bytes free > > (^ w/o the dots, obviously) > ‘SCREENSHOT’ [photo]: http://jen-lik.es/dirCw > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
On Friday, March 6, 2020, 05:20:05 p.m. EST, Louis Santillan wrote: > … “what does the following” > … “‘D:\> dir C:\*.* /w’” > … “return?” … [FDOS]·[GEMAPPS]···AUTOEXEC.BAT···COMMAND.COM···DEVICE.RAW FDCONFIG.SYS···GEM.BAT·KERNEL.SYS·NIC.TXT···SETUP.BAT SHELL.RAW···9 file(s)·252,897 bytes ·2 dir(s)···1,601,994,752 bytes free (^ w/o the dots, obviously) ‘SCREENSHOT’ [photo]: http://jen-lik.es/dirCw ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
sorry, last command should have been `D:\> dir C:\*.* /w` On Fri, Mar 6, 2020 at 2:19 PM Louis Santillan wrote: > > Also DOSes use a simple boot loader framework. > > BIOS loads Boot Sector from a disk > Boot Sector (in MBR format) loads additional OS boot code from file > system on a disk > OS Boot Code initializes machine, loads kernel/OS, and then loads > command interpreter that then loads boot config (config.sys, > autoexec.bat). > > FDISK creates an MBR formatted boot sector on a disk (can also flag a > particular partition as bootable). FDISK should do the same things > that GParted is doing. > FORMAT creates a filesystem pointed to by the MBR boot sector > SYS updates the MBR to contain bootable code and will also copy the > kernel/OS and command interpreter to the disk. > > So, in short, you just need to do (assuming you're booting off a > CD/DVD or something) > `D:\> fdisk` > (make one or more partitions with one of them being bootable, then, reboot) > `D:\> format C:` > `D:\> sys C:` > (then make any folders your want, copy any binaries, copy your > config.sys and autoexec.bat files) > > If any of these were missed, potentially, you could see a system that > is booting the way you're describing. From your booted DVD drive, > what does the following > `D:\> dir C:\*.* /a` > return? > > On Fri, Mar 6, 2020 at 1:52 PM Jen via Freedos-user > wrote: > > > > On Thursday, March 5, 2020, 06:05:49 p.m. EST, Dan Schmidt wrote > > > … “I would create a *2GB* boot partition and format it FAT16, and install > > > FreeDOS to it. My recollection is that FAT32 support was a work in > > > progress in FreeDOS when real development ended.” > > > … > > > “I think your fundamental problem is that FreeDOS cannot successfully > > > boot from a 7.8GB partition formatted as FAT32. It may be able to > > > access other larger partitions formatted FAT32 and seen by DOS as D:, > > > E: or the like, once FreeDOS *is* booted, but it cannot boot *from* > > > one.” … > > > > I tried this ↑ first – used GParted again to either rule it out or not as > > the issue, resized my C: partition (flagged as bootable) to 2GB, formatted > > it as FAT16 [This time it put 1.99 MiB unallocated ahead of it], and > > re‑installed FreeDOS from the DVD: same results. No biggie though; I > > don’t need more than 2GB anyway, so I’ll just leave it this size. > > · > > > > On Thursday, March 5, 2020, 06:05:49 p.m. EST, Dan Schmidt wrote: > > > “Try the utilities fdisk and format, I've not had any luck using Gparted > > > to make anything FreeDos can reliably read.”, > > On Thursday, March 5, 2020, 07:46:09 p.m. EST, Matej Horvat wrote: > > >… “I installed it manually with FDISK/FORMAT/SYS.” > > > > Next I tried using fdisk instead as suggested (↑,↑↑). I deleted the first > > partition, changed the display/entry units to cylinders, created a new > > partition located from cylinder 5 through cylinder 7669, formatted > > Partition 1 as FAT16 (option 6), set it as bootable, and made sure to write > > the table to disk before exiting. When I ran the FreeDOS install again > > after that, it wanted to to format again (first time it’s asked to do that > > – I’ve run the install several times now) so I guess I might’ve chosen the > > wrong FAT16 option? [GParted was detecting the filesystem type as unknown > > when I checked it before logging‑out of Arch Linux & shutting‑down] I > > typed “Yes” and it went ahead and supposedly formatted the partition as > > FAT32. When I checked it later however, it was showing‑up as FAT16 in both > > fdisk & GParted (which wasn’t showing it as anything before – weird), but > > bootable… restarted and STILL I get the black screen with cursor blinking. > > · > > > > On Friday, March 6, 2020, 01:31:53 p.m. EST, Louis Santillan wrote: > > > “As Matej mentioned, don't forget to ‘sys c:’ before rebooting after the > > > install.” > > > > I did not do that ↑. I ran the live disk again after and typed “sys c:” > > from the prompt (this is when I discovered the filesystem was FAT16 when > > the installation process via DVD had said it was reformatting as FAT32, as > > mentioned above^^). Should it matter? Do I need to try the installation > > again? Partition is showing as bootable. > > · > > > > On Friday, March 6, 2020, 01:36:34 p.m. EST, Jerome Shidel wrote: > > > “It is possible that the MBR contains incompatible boot code. > > > There are ways to force update it. > > > On FreeDOS 1.2 there was a ZAPMBR.BAT that would do that. I think it is > > > also included on 1.3-RC2. > > > I don’t recommend using it on a multi-boot system.” > > > > ↑ What if it’s one that’s *going* to be one, but FreeDOS is the first thing > > I’m installing? Could running that cause any harm? > > The hard drive I’m using is brand‑spanking‑new. FreeDOS is the first OS I > > (am trying to) put on this one. When I ran GParted the first time, it gave > > the an MS‑DOS/MBR layout, which came‑up as the default
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
Also DOSes use a simple boot loader framework. BIOS loads Boot Sector from a disk Boot Sector (in MBR format) loads additional OS boot code from file system on a disk OS Boot Code initializes machine, loads kernel/OS, and then loads command interpreter that then loads boot config (config.sys, autoexec.bat). FDISK creates an MBR formatted boot sector on a disk (can also flag a particular partition as bootable). FDISK should do the same things that GParted is doing. FORMAT creates a filesystem pointed to by the MBR boot sector SYS updates the MBR to contain bootable code and will also copy the kernel/OS and command interpreter to the disk. So, in short, you just need to do (assuming you're booting off a CD/DVD or something) `D:\> fdisk` (make one or more partitions with one of them being bootable, then, reboot) `D:\> format C:` `D:\> sys C:` (then make any folders your want, copy any binaries, copy your config.sys and autoexec.bat files) If any of these were missed, potentially, you could see a system that is booting the way you're describing. From your booted DVD drive, what does the following `D:\> dir C:\*.* /a` return? On Fri, Mar 6, 2020 at 1:52 PM Jen via Freedos-user wrote: > > On Thursday, March 5, 2020, 06:05:49 p.m. EST, Dan Schmidt wrote > > … “I would create a *2GB* boot partition and format it FAT16, and install > > FreeDOS to it. My recollection is that FAT32 support was a work in > > progress in FreeDOS when real development ended.” > > … > > “I think your fundamental problem is that FreeDOS cannot successfully > > boot from a 7.8GB partition formatted as FAT32. It may be able to > > access other larger partitions formatted FAT32 and seen by DOS as D:, > > E: or the like, once FreeDOS *is* booted, but it cannot boot *from* > > one.” … > > I tried this ↑ first – used GParted again to either rule it out or not as the > issue, resized my C: partition (flagged as bootable) to 2GB, formatted it as > FAT16 [This time it put 1.99 MiB unallocated ahead of it], and re‑installed > FreeDOS from the DVD: same results. No biggie though; I don’t need more > than 2GB anyway, so I’ll just leave it this size. > · > > On Thursday, March 5, 2020, 06:05:49 p.m. EST, Dan Schmidt wrote: > > “Try the utilities fdisk and format, I've not had any luck using Gparted to > > make anything FreeDos can reliably read.”, > On Thursday, March 5, 2020, 07:46:09 p.m. EST, Matej Horvat wrote: > >… “I installed it manually with FDISK/FORMAT/SYS.” > > Next I tried using fdisk instead as suggested (↑,↑↑). I deleted the first > partition, changed the display/entry units to cylinders, created a new > partition located from cylinder 5 through cylinder 7669, formatted Partition > 1 as FAT16 (option 6), set it as bootable, and made sure to write the table > to disk before exiting. When I ran the FreeDOS install again after that, it > wanted to to format again (first time it’s asked to do that – I’ve run the > install several times now) so I guess I might’ve chosen the wrong FAT16 > option? [GParted was detecting the filesystem type as unknown when I checked > it before logging‑out of Arch Linux & shutting‑down] I typed “Yes” and it > went ahead and supposedly formatted the partition as FAT32. When I checked > it later however, it was showing‑up as FAT16 in both fdisk & GParted (which > wasn’t showing it as anything before – weird), but bootable… restarted and > STILL I get the black screen with cursor blinking. > · > > On Friday, March 6, 2020, 01:31:53 p.m. EST, Louis Santillan wrote: > > “As Matej mentioned, don't forget to ‘sys c:’ before rebooting after the > > install.” > > I did not do that ↑. I ran the live disk again after and typed “sys c:” from > the prompt (this is when I discovered the filesystem was FAT16 when the > installation process via DVD had said it was reformatting as FAT32, as > mentioned above^^). Should it matter? Do I need to try the installation > again? Partition is showing as bootable. > · > > On Friday, March 6, 2020, 01:36:34 p.m. EST, Jerome Shidel wrote: > > “It is possible that the MBR contains incompatible boot code. > > There are ways to force update it. > > On FreeDOS 1.2 there was a ZAPMBR.BAT that would do that. I think it is > > also included on 1.3-RC2. > > I don’t recommend using it on a multi-boot system.” > > ↑ What if it’s one that’s *going* to be one, but FreeDOS is the first thing > I’m installing? Could running that cause any harm? > The hard drive I’m using is brand‑spanking‑new. FreeDOS is the first OS I > (am trying to) put on this one. When I ran GParted the first time, it gave > the an MS‑DOS/MBR layout, which came‑up as the default choice. > · > > Obviously I’m doing something wrong here. :P > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
On Thursday, March 5, 2020, 06:05:49 p.m. EST, Dan Schmidt wrote> … “I would create a *2GB* boot partition and format it FAT16, and install> FreeDOS to it. My recollection is that FAT32 support was a work in> progress in FreeDOS when real development ended.” > … > “I think your fundamental problem is that FreeDOS cannot successfully> boot from a 7.8GB partition formatted as FAT32. It may be able to> access other larger partitions formatted FAT32 and seen by DOS as D:,> E: or the like, once FreeDOS *is* booted, but it cannot boot *from*> one.” … I tried this ↑ first – used GParted again to either rule it out or not as the issue, resized my C: partition (flagged as bootable) to 2GB, formatted it as FAT16 [This time it put 1.99 MiB unallocated ahead of it], and re‑installed FreeDOS from the DVD: same results. No biggie though; I don’t need more than 2GB anyway, so I’ll just leave it this size.· On Thursday, March 5, 2020, 06:05:49 p.m. EST, Dan Schmidt wrote:> “Try the utilities fdisk and format, I've not had any luck using Gparted to make anything FreeDos can reliably read.”, On Thursday, March 5, 2020, 07:46:09 p.m. EST, Matej Horvat wrote:>… “I installed it manually with FDISK/FORMAT/SYS.” Next I tried using fdisk instead as suggested (↑,↑↑). I deleted the first partition, changed the display/entry units to cylinders, created a new partition located from cylinder 5 through cylinder 7669, formatted Partition 1 as FAT16 (option 6), set it as bootable, and made sure to write the table to disk before exiting. When I ran the FreeDOS install again after that, it wanted to to format again (first time it’s asked to do that – I’ve run the install several times now) so I guess I might’ve chosen the wrong FAT16 option? [GParted was detecting the filesystem type as unknown when I checked it before logging‑out of Arch Linux & shutting‑down] I typed “Yes” and it went ahead and supposedly formatted the partition as FAT32. When I checked it later however, it was showing‑up as FAT16 in both fdisk & GParted (which wasn’t showing it as anything before – weird), but bootable… restarted and STILL I get the black screen with cursor blinking. · On Friday, March 6, 2020, 01:31:53 p.m. EST, Louis Santillan wrote:> “As Matej mentioned, don't forget to ‘sys c:’ before rebooting after the install.” I did not do that ↑. I ran the live disk again after and typed “sys c:” from the prompt (this is when I discovered the filesystem was FAT16 when the installation process via DVD had said it was reformatting as FAT32, as mentioned above^^). Should it matter? Do I need to try the installation again? Partition is showing as bootable. · On Friday, March 6, 2020, 01:36:34 p.m. EST, Jerome Shidel wrote:> “It is possible that the MBR contains incompatible boot code.> There are ways to force update it.> On FreeDOS 1.2 there was a ZAPMBR.BAT that would do that. I think it is also included on 1.3-RC2. > I don’t recommend using it on a multi-boot system.” ↑ What if it’s one that’s *going* to be one, but FreeDOS is the first thing I’m installing? Could running that cause any harm? The hard drive I’m using is brand‑spanking‑new. FreeDOS is the first OS I (am trying to) put on this one. When I ran GParted the first time, it gave the an MS‑DOS/MBR layout, which came‑up as the default choice. · Obviously I’m doing something wrong here. :P ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
It is possible that the MBR contains incompatible boot code. There are ways to force update it. On FreeDOS 1.2 there was a ZAPMBR.BAT that would do that. I think it is also included on 1.3-RC2. I don’t recommend using it on a multi-boot system. > On Mar 5, 2020, at 7:45 PM, Matej Horvat wrote: > > On Fri, 06 Mar 2020 00:15:17 +0100, dmccunney > wrote: > >> I think your fundamental problem is that FreeDOS cannot successfully >> boot from a 7.8GB partition formatted as FAT32. It may be able to >> access other larger partitions formatted FAT32 and seen by DOS as D:, >> E: or the like, once FreeDOS *is* booted, but it cannot boot *from* >> one. > > No, the problem must be elsewhere. I have successfully booted and ran FreeDOS > from a FAT32 partition of almost 2 TB. I installed it manually with > FDISK/FORMAT/SYS. > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
As Matej mentioned, don't forget to `sys c:` before rebooting after the install. On Thu, Mar 5, 2020 at 4:45 PM Matej Horvat wrote: > > On Fri, 06 Mar 2020 00:15:17 +0100, dmccunney > wrote: > > > I think your fundamental problem is that FreeDOS cannot successfully > > boot from a 7.8GB partition formatted as FAT32. It may be able to > > access other larger partitions formatted FAT32 and seen by DOS as D:, > > E: or the like, once FreeDOS *is* booted, but it cannot boot *from* > > one. > > No, the problem must be elsewhere. I have successfully booted and ran > FreeDOS from a FAT32 partition of almost 2 TB. I installed it manually > with FDISK/FORMAT/SYS. > > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
On Fri, 06 Mar 2020 00:15:17 +0100, dmccunney wrote: I think your fundamental problem is that FreeDOS cannot successfully boot from a 7.8GB partition formatted as FAT32. It may be able to access other larger partitions formatted FAT32 and seen by DOS as D:, E: or the like, once FreeDOS *is* booted, but it cannot boot *from* one. No, the problem must be elsewhere. I have successfully booted and ran FreeDOS from a FAT32 partition of almost 2 TB. I installed it manually with FDISK/FORMAT/SYS. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
On Thu, Mar 5, 2020 at 5:25 PM Jen via Freedos-user wrote: > I haven’t tried reformatting the partition and running the installation again > yet; I suspect it will still do the same thing. Should I try that? > Any ideas what I’ve done wrong or why it might not be working? You may need to reformat. I installed FreeDOS years back on the hard drive of an ancient notebook I had been given. I partitioned the HD to have a 20GB slice formatted NTFS from which I booted Win2K, a couple of 8GB slices formatted as Linux ext4 from which I booted Ubuntu and Puppy Linux, a swap partition for the Linux OSes, respectively, and a 2GB partition formatted as FAT32 where I installed FreeDOS. I used Linux Grub2 to create a boot menu from which I could boot the chosen OS at runtime. I had to do a *lot* of fiddling to successfully boot FreeDOS in that configuration, and I don't even know just which fiddle did the trick. (A problem which required reinstalling Win2K broke it and I never did get it to work again.) I would create a *2GB* boot partition and format it FAT16, and install FreeDOS to it. My recollection is that FAT32 support was a work in progress in FreeDOS when real development ended. DOS dated from the days of FAT16, and a 2GB volume was the largest one DOS could access. FAT32 was developed precisely to remove the need to create lots of 2GB volumes seen as separate drives so DOS could access them, but Windows 3.X was already in common deployment, and FAT32 was intended to make life easier for Windows. I think your fundamental problem is that FreeDOS cannot successfully boot from a 7.8GB partition formatted as FAT32. It may be able to access other larger partitions formatted FAT32 and seen by DOS as D:, E: or the like, once FreeDOS *is* booted, but it cannot boot *from* one. > --- Jen __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
Try the utilities fdisk and format, I've not had any luck using Gparted to make anything FreeDos can reliably read. On Thu, Mar 5, 2020 at 3:25 PM Jen via Freedos-user < freedos-user@lists.sourceforge.net> wrote: > I’m trying to install FreeDOS onto the SSD hard drive of my ThinkPad W520 > 4284‑WZN copied to RAM from a DVD I have, using its internal DVD‑RW > drive. > *·* In the UEFI BIOS *[version 8BET62WW (1.42)]*, I set the boot to “*Legacy > Only*” & the ‘SATA Controller Mode Option’ to “*Compatibility*” *mode* (*IDE > mode*). Reserved memory for UEFI Boot Manager has been disabled. > *·* Using GParted on the latest 64‑bit version of SystemRescueCD *(6.1.0)*, > I then made a *FAT32* partition as the very *first* partition (*C:\*) > with 1 MiB free space preceding it, aligned to ‘*Cylinder*’, and made it > 7.8 GB (7,439 MiB / 7.26 GiB), and labeled it as *“DOS”*. > *·* After that, I inserted the FreeDOS DVD and selected the options to > install everything to the C:\ drive, which all seemed to go well. > *·* Upon rebooting however (or from cold boot), *all I get is an empty > black screen with a flashing underscore cursor*. I’ve hit *F12* on > startup to bring up the Boot device List to ensure the hard drive is > selected, and have tried restarting a number of times but never get > anything other than the empty black screen with the blinking cursor of > death. I’ve walked away for a long time and come back, but nothing ever > winds‑up loading – cursor continues to blink. I’ve gone back into BIOS > to ensure that all the options I changed saved properly and have not reset > themselves to defaults; everything appears as I configured it. > *·* I reinserted the live CD and from the FreeDOS prompt, ran the command > “bootfix c:”. It did not fix the problem. > > I haven’t tried reformatting the partition and running the installation > again yet; I suspect it will still do the same thing. Should I try that? > Any ideas what I’ve done wrong or why it might not be working? > > Thanks in advance for any help you might be able to offer, > > --- Jen > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Only Get Black Screen with Blinking Cursor following Installation of FreeDOS to my Machine
I’m trying to install FreeDOS onto the SSD hard drive of my ThinkPad W520 4284‑WZN copied to RAM from a DVD I have, using its internal DVD‑RW drive. · In the UEFI BIOS [version 8BET62WW (1.42)], I set the boot to “Legacy Only” & the ‘SATA Controller Mode Option’ to “Compatibility” mode (IDE mode). Reserved memory for UEFI Boot Manager has been disabled. · Using GParted on the latest 64‑bit version of SystemRescueCD (6.1.0), I then made a FAT32 partition as the very first partition (C:\) with 1 MiB free space preceding it, aligned to ‘Cylinder’, and made it 7.8 GB (7,439 MiB / 7.26 GiB), and labeled it as “DOS”. · After that, I inserted the FreeDOS DVD and selected the options to install everything to the C:\ drive, which all seemed to go well. · Upon rebooting however (or from cold boot), all I get is an empty black screen with a flashing underscore cursor. I’ve hit F12 on startup to bring up the Boot device List to ensure the hard drive is selected, and have tried restarting a number of times but never get anything other than the empty black screen with the blinking cursor of death. I’ve walked away for a long time and come back, but nothing ever winds‑up loading – cursor continues to blink. I’ve gone back into BIOS to ensure that all the options I changed saved properly and have not reset themselves to defaults; everything appears as I configured it. · I reinserted the live CD and from the FreeDOS prompt, ran the command “bootfix c:”. It did not fix the problem. I haven’t tried reformatting the partition and running the installation again yet; I suspect it will still do the same thing. Should I try that? Any ideas what I’ve done wrong or why it might not be working? Thanks in advance for any help you might be able to offer, --- Jen___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
