2020. 2. 20. 02:56ㆍ카테고리 없음
Not too many years ago if you wanted to, test to see if a repair CD you downloaded worked or whether your custom made Windows install disc could boot, you had to burn the content to CD or DVD and then reboot your computer to try it out. This not only took vast amounts of time waiting for the disc to burn but it also meant perhaps fiddling with the boot order in the BIOS and if you didn’t have any rewritable media, every burn would cost you money.These days disc images (ISOs) are everywhere and that allows you to do several things such as like before, or even to test without leaving your desktop. The trouble is using the above methods to boot the ISO image can still take time which isn’t ideal if for example you quickly want to try a number of the latest Linux distros. Being able to boot and test an ISO image with just a couple of clicks of your mouse can be a real time saver, here we show you 3 ways to do it. MobaLiveCDMobaLiveCD is a freeware tool that will run your Live or bootable disc images directly from within Windows with just a couple of clicks of your mouse. This is thanks to the small and open source virtual machine emulator QEMU. The program itself is portable and only 1.5MB in size which is quite impressive.Not only will it start bootable CD ISO images but with the last update to version 2.1 you can also launch a bootable USB flash drive which is useful when you’re testing if your multi boot or installation USB works before trying it for real.
MobaLiveCD is simplicity to use, all you have to do is run it (Run as administrator if you have UAC on) and either press “Run the LiveCD” and browse for the ISO image file, or click “Run the LiveUSB” and choose the letter of your flash drive.The program will then launch QEMU with a predefined configuration and begin the boot process. To interact with the emulated operating system, click in the window, press Ctrl + Alt to get out again. The “Right-click menu” button usually doesn’t work in Windows 7 or 8 because they recognise the ISO file type by default and already have other programs associated with it, Vista and XP will work if their ISO file type hasn’t already been taken over by another program.Although MobaLiveCD is small and easy to use it does have drawbacks. Firstly the QEMU program it relies on emulates very low end hardware. It does use up to 1GB of memory but the CPU being emulated is a Pentium II 333Mhz which makes things sluggish during boot and inside the live operating system. As a simple example we booted in MobaLiveCD and VirtualBox, MobaLiveCD took 2 minutes 10 seconds to boot to the desktop, VirtualBox took only 33 seconds.Also, because there has been no updates since 2009 it will sometimes fail to boot an ISO image or USB flash drive correctly, likely due to a now rather outdated version of QEMU. MobaLiveCD is still compact and useful but its mileage depends entirely on whether you can get it to work, an update would definitely be welcome but sadly the project appears to have been pretty much abandoned.2.
Boot an ISO Image Directly From VirtualBoxVirtualBox is a hugely popular free software to create and run virtual operating systems and it can run a virtual CD/DVD disc inside a virtual machine (VM) by using the computer’s real optical drive or an ISO image. This is ideal for booting and testing an ISO but there are a several steps to go through each time you want to boot a different image. Here we show you how to setup a virtual machine and be able to run ISO files with a few clicks.1. If you don’t already have it,. Note we have tried this method with and it doesn’t work.2.
Run the program and click New to create a new machine, name it ISOBoot. You MUST use ISOBoot (including capitals) or you will have to manually edit things later on. For Type/Version use anything you like.3. Allocate enough memory to allow the ISO images to boot, 512MB-1GB should be plenty. Choose “Do not add a virtual hard drive” and click Create.4.
Now with the new VM selected click Storage on the right, click the Empty drive in the Storage Tree and change from IDE Secondary Master to IDE Primary Master in the CD/DVD Drive dropdown menu. Click OK and close VirtualBox.5. The trick is to make VirtualBox load and boot an ISO image from the desktop without you having to launch the program first, go into Storage settings and manually browse for the file every time. Download the following file:The batch file injects the selected ISO filename into the ISOBoot virtual machine and then automatically runs it which boots to the ISO image. You can either drop an ISO file onto the BAT icon or launch it as a command.
To make things easier, copy the BAT file to:C:Programs FilesOracleVirtualBoxThen download the zip file below, open it and double click the Install file to import the data into your registry:This creates a context menu entry so when you right click on an ISO file in Explorer a menu entry will allow you to click and run the ISO file inside VirtualBox automatically. Run RemoveISObootVirtualBox.reg from the Zip to remove the context menu entry.When you have finished simply power off the VM. These files rely on VirtualBox being installed to the default locations, you will need to manually edit them if this isn’t the case. If you don’t see the right click entry it could be that another program has taken over the ISO file type in which case you will need to edit the registry file yourself. Have a look at the (Default) Data value in HKEYCLASSESROOT.iso to see what has taken over from the default of “Windows.IsoFile” and adjust the registry file accordingly.3. Boot an ISO Image Directly From VMware PlayerVMware Player is also a popular free virtualization software although we prefer VirtualBox because of the valuable snapshot facility.
Microsoft Windows 7 Free Download
It can also be configured to automatically boot to an ISO image in a similar way, here’s how.1. If you haven’t already, (near the bottom of the download page).2. Launch VMPlayer and click “Create a New Virtual Machine”. Select “I will install the operating system later” and then Next.
For the Guest operating system select Other/Other (Important!) and click Next again.3. Name the virtual machine ISOBoot and click Next. At the Disk Capacity screen you can leave the default of 8GB, this won’t be used as you are not using the virtual hard drive. Click Next - Finish and close VMPlayer, things like usable memory can be edited later on.4. 1 more way to run bootable ISO image files directly in Windows: QEMU, directly.Using ‘helpers’ (MobaLiveCD etc.) to run QEMU is for kids. MobaLiveCD right-click is a ‘wrong-click’, it fails many times More: I never had any speed problems with QEMU.Also: there’s newer versions of it than you mention!
Latest releases: 2.9.0 Apr 20 2017, 2.8.1.1 Apr 20 2017, 2.7.1 Dec 23 2016, 2.6.2 Sep 29 2016. So, it seems the project is very much alive! Read about in their new website: qemu.org/index.htmlGreat article otherwise. Topic 2 and 3 are ok.
Hello,It appears that tomorrow (1/28/14) I'll be receiving my BladeRF. I'm obviously looking forward to this greatly. It'll be Wednesday before I can start to work on getting it installed. When I do I will be installing it on two different machines. One runs Windows 8.1 64 bit and I will attempt to make it work with USB 3.0 via an Intel chipset.
The second will be a Windows 7 Pro SP1 32 bit machine that has a Renasys chipset USB 3.0 PCI-E card installed, the one referenced at. I have located the Windows Installer.exe file on the Nuand support page. I understand the issues with unsigned drivers and Windows 8.1 and expect I'll be able to work around that. I will ultimately use my BladeRF with Simon's SDR-Radio software at for spectrum display and signal tuning throughout the device's frequency range.But of course, until I get the darned thing properly installed that ain't gonna happen.So my question is as the topic states, is there somewhere a definitive Windows install method for the bladeRF, a sequence of how things should be done in order to meet with success.
Simon clearly has SDR-Radio working with it, and the blog at VK4ZXI has some interesting info as well not only about the install but also about using it with SDR-Radio.just not a complete 'here's how you do this from A to Z', unless I'm just missing it. I'm guessing the basic procedure is to run the installer, plug in the card, check it at the command line, and load the fpga? Surely it's not that simple.or is it? I've never loaded an fpga, so I don't know what the instructions are to do so.
Maybe there's a readme in the folder where the files are installed? I haven't tried running it yet because I wasn't sure if the software should be run first followed by the card being plugged in.or vice versa?I would also like to help with documenting this procedure so future users have a guideline to follow, by perhaps providing a step by step tutorial with screenshots. Obviously I could provide this for both Windows 8.1 and Windows 7 users. If I can get a definitive hand-hold in the right direction, I'd be very happy to be able to do that. I'm a radio hobbyist, and I can assure you that there are A LOT of radio hobbyists that are cutting their teeth on the RTL dongles that have become available, and some of them like me are looking to replace those $20 gems with a quality piece of gear. Enter bladeRF in my case.Any help greatly appreciated, as this is turning into the 'War and Peace' of postings.I'll stop now.Thanks,ScottWebmaster - Scan New England.
Yum Install Gnuradio
Given that I'm hacking on the code, I usually build from source - I haven't given the Windows installer a test drive yet.However, I asked the gentleman that puts together the windows installer to build the latest and greatest, given that there have been firmware, FPGA, and host-side fixes and improvements since the last installer was posted. The v1.2 installer is fresh out of the oven, but not yet tested I believe:I've asked him to post back here detailing the procedure for using it and getting the device upgraded with the lastest firmware and FPGA image. I'll also do my best to test drive the installer and SDR-Radio installation tonight and post back, if he doesn't beat me to it.If you'd like to trudge ahead in the meantime, the worst case scenario that I can think of is that you might need re-run a bladeRF installer. (I've also been told that the installer creates a restore point, for what it's worth.)A common item of confusion for people is which FPGA and FX3 version to use, given the libbladeRF version they have installed. As of late, the comments on the and the try to make this clear. However, if you run into confusion, feel free to ask here. (Or hop on the #bladerf channel on to ask someone in real-time)If you go with the latest installer, you'll want FPGA version v0.0.2, and firmware version v1.6.1.From my understanding, the device does not need to be plugged in when you run the installer.
However, I belive it will ask if you want to upgrade your firmware, so I assume there's a prompt to plug the device in when you get to that point.Sorry that's not quite the answer you're looking for.but we'll get you up and running soon, and get that wiki updated to cover the Windows installer procedure. Thanks guys, I appreciate the info and I'll go with jynik's recommendations. I do intend to try to properly learn gnuradio in Linux, just not at that point yet. I've been trying to get things going with my rtl dongles on Linux but it's just not happening yet. That's another topic for another thread.probably in another forum.I will indeed trudge ahead and follow up with results.Naturally after posting my original message last night I have found this:I expect this gentleman is a member of this forum as well, and this seems like a helpful guideline.
I still would like to provide some help as well for those who will follow in Windows, so I'll do what I can as well.Regards,Scott. The install is actually quite easy with the new Windows installer. When it comes to USB 2.0 anyway.USB 3.0 appears not to work at all, but this isn't the first time this statement has been made from my research. But I'll figure that out eventually.As it stands now, I have the BladeRF running in Windows 7 with SDR-Radio version 2.1 build 1640. I did a step by step with screenshots which I will put together and share. Updating firmware and flashing FPGA is a simple process although a bit different (and easier) than what I saw and read about the earlier installer.Ironically with the USB 3.0 issue, when plugged into a USB 2.0 port, Windows indicates that BladeRF will run faster connected to a USB 3.0 device.ya think? I'm running the PCI-E card that I mentioned in my earlier post, which was part of a known working USB 3.0 configuration.
Well, not yet in my case.But it's a start. Success with Windows 7. Now, on to Windows 8.1. Thanks again.Scott.
And.I have it working in Windows 8.1! However.I was able to connect right off the bat with USB 3.0. But when I ran SDR-Radio the interference was so bad it was absolutely unusable.
I relocated it to a USB port and it seems to be OK now, but about 10 MHz is as wide as I can get. So obviously I have A LOT to learn with this device. As with Windows 7 I did a step by step of screenshots. Unlike Windows 7 bladeRF-cli.exe does not wind up on the start menu and it is necessary to drill down into c:Program Files (x86)bladerfx32 or x64 to find it. I chose the x64 folder as this is a 64 bit machine (despite the fact that the install is in the x86 Program Files folder). I was able to figure out that I had to run bladerf-cli -i to get to the bladerf prompt, and then everything was fine from there both in USB 3.0 and USB 2.0.I have read elsewhere that USB 3.0 interference is bad, but THAT bad. Wow, it definitely renders this device unusable.
I'm guessing the fact that I have a 'naked' bladeRF sitting on the shelf next to the PC can't be helping. I also have a lot to learn about SDR-Radio's settings for the bladeRF, but this is obviously not the forum for that and I'll address it at Simon's Yahoo Group.But it is definitely reassuring to see just how easy it is to get this running in Windows. I just hope the USB 3.0 issues can be solved. I will get the specifics of my setup in print so they can be added to the working configuration section of the Wiki.if you accept that 'working configuration' includes the horrendous interference.More to follow. Well.it would appear that something at home is causing my interference problem, whether it be USB 3.0 or otherwise. I'm at work, and I am running the bladeRF on a Windows 7 64 bit machine with USB 3.0 this morning and looking at 30 MHz of spectrum without any problems at all.Chipset in this case is an Intel 8 Series/C220 Series USB Enhanced Host ControllerPerformance is absolutely flawless.I guess I'll have to move into work if I want to use bladeRF to the fullest of its capability. So without a doubt now, the device itself is fine, the USB 3.0 cable supplied is fine, and I have some work to do at home to track down my interference issue.
I suspect it's the Dell Windows 8.1 PC itself and something is funky with its USB 3.0 connectivity. Unfortunate, but I'll plug away at it. I may try moving the Renesas PCI-E card into the 8.1 PC to see how it does.Scott.