Re: Biosagentplus With License Key 70

0 views
Skip to first unread message
Message has been deleted

Canumil Flowers

unread,
Jul 13, 2024, 12:25:32 AM7/13/24
to chipzetscase

I have been wanting to switch to Linux for many years, and I finally took the step to download a Fedora 30 KDE live CD iso (actually USB) and give a try installing it. Since this is the computer I use for work, I want to keep a dual-boot system with Windows 7, at least during a transition period. The installation has not been successful though, and after spending all day today trying to figure out what might be the problem I found this video: Install Fedora 23 in Legacy Mode (Dual Boot Windows 7/8/10) - YouTube which was very helpful.

So my USB boots in UEFI mode, but I would like to install it in legacy BIOS mode. Is there any way to do this? Can I burn the USB in a different way so that it would boot in legacy mode, or can I add a configuration switch somewhere?

Biosagentplus With License Key 70


DOWNLOAD https://urloso.com/2yMyxF



is there a way to change this command to make it run the legacy mode? i tried changing linuxefi to linux and initrdefi to initrd and run Ctrl-x, and the system did start, but I get the same errors as before with anaconda still trying to install and EFI system.

In my bios at least i can choise the option 1 or 2. If i select the option 1 i am only disponible to install in UEFI mode so that when I place the usb only can see UEFI:USB install. If I choise the option 2 I will can choise into 2 options when I place the USB:

I think you do need check your configuration into the BIOS. The only thing what is strange to me about it that you did comment is what if you can run only UEFI How is windows 7 loading in mode BIOS, it is what is chocking me.

Yes, I went to my HP BIOS manual and I double checked that the settings are enabled to be able to run both. As my boot loader is a bit fucked up atm, I need to get to the BIOS boot menu to start the system anyways, and the options I can choose there are (the comments in parenthesis are mine) :

Yes!!!
Thank you so much. The USB that RUFUS burned finally was able to be loaded in legacy BIOS mode and after that it was a 10 minute smooth ride to a successfull installation. Now I have a fully functional dual boot.

4. BIOS Update (I have BIOS Phoenix F.34), but BIOSAgentPlus on PhoenixBIOS.com told me that I can Update my BIOS, where I can take it and what version (I can`t buy BIOSAgentPlus Account)? Please HELP!

My Videocard nVIDIA GeForce 8400M GS 256Mb really have PCI Express and I can put it out and put in more powerfull Videocard or there is no PCI Express and if I need to update Video - one chance is REBALL the Chip?

The graphics adapter is soldered to the motherboard and cannot be removed or replaced. It doesn't matter what any software program is telling you. There is no removable graphics 'card' in your notebook.

5. Your notebook is not supported by HP for W7, W8 or W8.1, so I imagine there is a driver problem of some kind or another with which I would not be able to help you with as there is probably no solution to it.

I use Windows 7 image backup, Acronis True Image and Macrium Reflect to create rescue disks but I can not reach the BIOS setup screen to set the BIOS to boot first from the DVD so I can not boot to a rescue disk in the DVD drive. This machine is not safe without the ability to boot from the DVD.

You can use these $2 adaptors, with keyboards that support USB and PS/2. These keyboards(or mice) auto-detect which protocol to use at power-up, based on the responses they get from the computer at that time. This is all done by the keyboard controller chip at power-up handshaking time, and once the protocol is decided upon, the controller remains in that state while powered, which means that the keyboard controller will not be able to run in PS2 mode for the BIOS screen but then switch to USB mode after Windows starts and the USB drivers load.

I have a really old set of notes for recovering a bricked BIOS that can be tried. Since BIOS have changed since then to the 4000 series Gateway days you will have to adjust. Before that I would try resetting the CMOS either via the jumper or battery removal.

Download the newest BIOS from the Intel site for your motherboard.
Put the downloaded Intel's flash BIOS on a bootable diskette. (see the text files in the zip-file on how to do it)
Go into the BIOS and enable the option 'Check for User Flash ROMS' (it's in SETUP)
Power down the computer
Set the BIOS Jumper on the motherboard to RECOVERY
Insert the bootable diskette you made in step 2 that contains the new BIOS
Turn on the computer
It'll now go through the recovery procedure and then load the new BIOS from the diskette.
After that the recovery procedure is completed, power down
Set the BIOS Jumper back to the normal mode
Power up

This is where I must caution you, Be Absolutely sure the first part of the string matches. From there, for the non- technically challenged get a copy of Intel's integrator toolkit to look at the actual bios information to find out if the new bios info is correct. ie; if you have a micro ATX the new bios may contain the commands for 5 PCI slots, instead of 3. I found this out the hard way. Luckily I recovered.

Next, get the bios recovery instructions for your Intel board, (normally this would entail removing the bios jumper from the board). Then, D/L the Bios recovery file from Intel, onto a formatted floppy disk, *note* it does not have to be bootable.

After this, set your board for bios recovery, after you turn it off of course, insert the floppy and restart. THERE WILL BE NO VIDEO AT THIS POINT, so don't freak, and especially don't turn off the machine. It should turn off automatically, or give you a beep code [2 beeps?] when done, in any case, watch the status indicator on the floppy drive.

With an Intel board, all you'll need is just the .bio file on a non bootable floppy (the bios will automatically look for the file on the A: drive) Set the board to bios recovery mode (generally this would entail removing the bios jumper), insert the floppy and wait.
DO NOT turn off the machine, it should shut off by itself, or beep twice when done.

As I stated before, Be VERY careful to match your bios with the like bios from Intel. Especially if you have a micro atx (I learned this the hard way) You can use Intel's integrator toolkit to view the info.

The Intel Integrator Toolkit is a utility for PC OEMs and professional system integrators building systems with Intel Desktop Boards. This application helps streamline and automate the manufacturing process while allowing replication of customized system configurations.

There seems to be a catch 22 in all of this. To flash the BIOS you have to set the BIOS to look for the update file. You have to get to the BIOS setup screen in order to do this. Then you move a jumper and re-boot. But, I can't get to the setup page so I can't set the BIOS to look for the update file. I might be stuck. I see from following your last link that the Intel Integrator Toolkit support for this motherboard has ended.

1. Since it does not seem that I have a UEFI BIOS in this box I wonder if the BIOS setup will start if I wipe the CMOS memory by pulling the battery and disconnecting the disk "0" hard drive so it won't find Windows? It seems that this would be what would happen if I just replaced the coin battery anyway.

Maybe it's time to buy a whole new machine with Windows 10 and then get this box running with Linux. To an old mainframer like me it seems ridiculous that these things have a service life of about 6 years.

So like I said I configured it wrong once (I did put a jumper on the 1-2 pins of "JP11" instead of "JP12"), the PC booted, I did check if I could enable write-back cache and of course, I was able to do this. Then I booted DOS and started speedsys and then I discovered that the CPU was detected as a DX4 (here is where I figured out it was configured incorrectly). I finished the benchmark (I wanted to see how many MB/sec I earned in comparison to the previous DX4 chip which only had 8KB of Write-through cache) and there was a slight difference there. But since it's a 5x86, I did put the right configuration for it as says the motherboard's documentation. And here is where problems are begining. First I went into the bios and I saw that the Write-Back setting for L1 cache was not accessible anymore, then I still wanted to boot on my HDD ... but now once it has tested the ram and after the first floppy disk drive (I've got two fdd), the computer freezes and the second fdd is making the disk to spin and the access light stays on. The keyboard doesn't respond either, so this is a total crash of the machine.

As you may see on the photo, the "JP12" is placed incorrectly. (2-3 instead of 1-2 for AMD's 5x86) and that's just because I wanted to check if they just misplaced the jumper on the documentation, but it didn't help ...

Sure I'm using a heatsink with a fan (if you look at the bottom right corner, you can see it's plugged to the motherboard). I've not checked for bios updates but yeah this might help, I don't know. My motherboard was made in late 1995 (the DX4 it came with even had a "Designed for windows 95" instead of "designed for microsoft windows") but since the 5x86 was released really late that year, maybe it's not in the "CPU list" of the motherboard just like some 775 motherboards won't boot with a socket 771 Xeon installed unless you patch the bios with newer microcodes

b1e95dc632
Reply all
Reply to author
Forward
0 new messages