Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by hooovahh

  1. There is no emoticon which conveys my astonishment.
  2. I have never discovered a programming language that can do what I need it to do, and be as quick, and easy to use as LabVIEW. No language is perfect, but for me and what I need from a programming language, LabVIEW is the only choice. And when ever any one questions LabVIEW's abilities, I always ask them to write a Hello World program, in LabVIEW it takes me less than 15 seconds to create and run a hello world program. Some languages would take longer than 15 seconds just to compile it. Also it's troubleshooting abilities are amazing. I learned to program with LabVIEW, then when I went to Java I had a huge difficulty in finding where problems were. With LabVIEW just highlight execution and you can see exactly what is happening.
  3. hooovahh


    QUOTE(crelf @ Jun 2 2007, 05:14 PM) Yeah you actually have to pay to download. I'm not a member of that highly illigal service but I was curious and found it cost money. It is very discouraging having people not spelling LabVIEW correctly. I'm not a big stickler on capitalization, but that would be like trying to say Java but saying Lava. People would definatly get confused if they were searching Lava and got directed here on accident.
  4. QUOTE(Wiebe@CARYA @ May 16 2007, 12:19 PM) Okay I don't want to turn this into a BartPE thread so I won't, but I will answer your question as briefly as possible. A while back, when XP was still in beta, a guy named Bart Lagerweij realized that during the normal XP install it kinda goes into a "Pre-Install Environment" where you have mouse and keyboard detection (this is the part of the install where you give it the serial number and other information) he realized by taking the right files from the installer CD he could have a machine boot to a live environment which was a preinstall environment where the user has HD detection, mouse keyboard monitor, and other basic functions. He made a program that would automate creating this Live environment and called it PEBuilder. PEBuilder would basically make BartPE from a XP (or Windows 2003) installation CD. This environment is very limited, it doesn't look like XP at all, it just has the basic funcitonality of XP. He then made plugins which make BartPE look and act more like XP. There's been several different spin offs of BartPE with Bart's permission, Reatogo, Winbuilder, and several others which are built around BartPE. As for the legality. The basic rule of thumb is, if you own a legal copy of XP you can legally make a backup copy incase your original is damaged. Because of this you can make legal copies of XP system files, you CANNOT however make tons of BartPE CDs and give them to all your friends (legally) it would be like giveing them copies of Microsoft software. So giving it to others is bad, but using it your self can also be kinda hazy. I am not a lawer and have no legal back ground. So any thing I say about the law could be completely wrong. Because of that I don't want to say what is fair use on a personal level. For system rescue on a few of your own personal computers BartPE should be fine. But making it the primary OS for 500 computers! I can't see how Microsoft would approve of that. There are actually limitations on some of the XP install files that say after 24 hours of being on it will turn the computer off. Kind of a bummer but it prevents people from making BartPE the primary OS (there are work arounds but non that are legal that I know of) For more legal discussion of BartPE go here. http://www.911cd.net/forums//index.php?sho...ost&p=56546 If you're still confused send Bart an email, in my experience he's very friendly, and has even helped my company with random questions we had about DOS boot ables a while back.
  5. I don't own a mac but a friend of mine does, he dual boots with boot camp. I don't see how there would be any problems with running LabVIEW inside windows while on a mac. I mean windows doesn't know it's running on a mac, it just looks for an x86 architecture and drivers to control hardware, as long as it has these things I don't see why it wouldn't work.
  6. Yes also the NI Example Finder has a couple email examples but you can't find them by searching for email. Under tasks it is found by going to Networking, then Internet & Web.
  7. QUOTE(crelf @ May 11 2007, 09:34 AM) No it's okay I just won't speak any more.
  8. Wow this is fricken amazing. I had no idea that this kind of thing existed. But yes it is kinda odd that NI would allow such a thing. Maybe NI makes most of their profit off of the hardware. I mean LabVIEW isn't the best programming language unless you add on all the DAQ, and Real-Time Embedded support that NI gives it with the hardware that they provide. I'm in the process of trying it out right now, I'm really curious to see how fast it runs. I mean the concept of running a virtual machine over the internet is not a new concept. I can't seem to find the link now, but there is a version of Linux that you can run from within a browser, but it's not free so I never tried it.
  9. QUOTE(Wiebe@CARYA @ May 8 2007, 11:33 AM) BartPE is Free and Legal when used properly (you would be using it properly) BartPE is not owned by Microsoft. I think you are getting WinPE and BartPE mixed up. If you're interested here's the BartPE home page. http://www.nu2.nu/pebuilder/''>http://www.nu2.nu/pebuilder/' target="_blank">http://www.nu2.nu/pebuilder/ But as I mentioned earlier BartPE probably wouldn't work because of the ethernet drivers issue. BartPE would need the drivers for the specific ethernet card. Usually this is done by running a small utility from within Windows, and extracting the driver that way. But since these machines don't have windows install it would make it more difficult to get the right drivers.
  10. I'm not trying to flame you but isn't rule number 1 of LabVIEW to have data flow from left to right? Maybe you were in a hurry, but I found it difficult to understand what was happening in your VI because information didn't flow. Also there were no comments. What is Count? is it simply the number of rows in the array? What is Count good for? What version of LabVIEW was it made with? Why is there a random constant of "0" in the middle of the while loop which isn't wired to any thing? Answering any of these would be greatly appriciated. I'd also be glad to show you where you code could be improved if you'd like.
  11. QUOTE(crelf @ May 4 2007, 12:53 PM) Not necessarily, I am very cautious about posting here.
  12. QUOTE(dannyt @ May 2 2007, 06:41 AM) I know what you mean, at other forums I don't mind being funny, and kinda poking at people in a non threatning way (like making fun of crelf because he would know I'm kidding) But here I feel nervous about every thing I post, (being fairly new here doesn't help either) but crelf assured me, just read the Guidelines http://wiki.lavag.org/index.php/Forum_Guidelines''>http://wiki.lavag.org/index.php/Forum_Guidelines' target="_blank">http://wiki.lavag.org/index.php/Forum_Guidelines and if you don't break any of the rules feel free to post. Of course there are quite a few rules, but there needs to be since we don't want this to turn into the NI forums. Not that it's NI's fault people abuse it. (is this off topic I don't want to break the rules)
  13. Yes the easiest (and ugliest) solution I would suggest, is similar to what you said. If the machine you are plugging it into is very controlled, meaning you're not constantly plugging USB drives, and installing new drives, I guess you could have it in a while loop, trying to get the file size of say F:\autorun.inf or some thing on the USB drive. It would return an error until the drive and file exists. That would be wasting alot of resources even if the while loop only ran once a second. It would have to be event driven since it could go hours, or days before being plugged in. Also another suggestion that you might want to look into is you could have the VI do some thing similar to "Wait Until Active" (which I don't know how to implement) Because as I'm sure you already know, when you plug in a USB drive that auto run menu opens. I don't know if LabVIEW supports it or not but you could create an event that does nothing until that auto run window is active then do stuff.
  14. hooovahh


    I must say I'm quite impressed (it happens alot) I was trying to find a way to trim MP3 files (cut off 6seconds from the beginning) and was hoping your code could help me, but I see it basically uses alot of Call Library Function Nodes. Also I had it crash several times even with LabVIEW 7.1. If I opened LabVIEW and told it to open the VI it would crash. But if I double clicked the file (when LabVIEW wasn't running) it would open LabVIEW and the VI properly.
  15. Okay after I pretty much already have a set up done I realize it won't work for you. My idea was to take a PreInstall environment, based on BartPE, where you would create a live OS which was around 80MB. You could then load that 80MB into ram and run any LabVIEW executable with it. The problem is at 80MB there aren't very many drivers, it would likely not have any audio, dial-up, wireless, very limited ethernet drivers, but it would have SATA drives, and USB mass storage drivers. So I was going to include this program for you to include the ethernet drivers in the package. So basically you run this little utility, and it will detect what kind of drivers you have installed, then it gives you the option of adding those drivers. So my idea was for you to run this utility on the machine that you wanted to work on. Problem is, that computer doesn't have windows on it, it doesn't have any OS on it. This is a perfect solution, IF the identical ethernet card is also on another machine that does have windows on it. I know it's kinda confusing but it's hard to explain too. If you're still confused I can elaberate. Also if you still would like a How-To load LabVIEW into RAM I can post that some where, who knows some one else might want to do some thing similar.
  16. QUOTE(Bryan @ Apr 16 2007, 03:00 AM) I'll make a how to in a little bit here but I have some questions about exactly what you are trying to accomplish with this. I realize what you want to do, but I would like to know why. From what I gather you want to run a compiled LabVIEW executable on several machines at once, and they will be connected through a network. Why do you want it to be running in RAM? These machines you want to run the exe on, do they have a Windows operating system? What version of LabVIEW was used to make the compiled exe? I ask these things because, if these machines already have windows, and you're simply looking for an alternative to installing the LabVIEW Run-Time engine, you can get around this by putting the right dlls and files into a directory, and your exe will run with out the Run-Time engine installed. It's kinda tricky and won't work for every executable but it's worth a try. If you're looking to run the exe in ram because it would be fast, you can create a ram drive in Windows fairly easily. From there you can copy your executable to the ram drive and BAM, it will run fast.
  17. QUOTE(crelf @ Apr 14 2007, 01:37 PM) Oh you're only saying that because you work for some big hot shot company that NI cares about. Me speaking from no experience what so ever of course. //Yes I know, I know
  18. Okay I did some quick testing. I was able to boot a windows like OS into ram, and run a LabVIEW 6.1 compiled file. This "windows like" os is actually BartPE but it contains the Explorer shell so it looks very much like windows. It also contains every thing you should need to run what you'd like. It has notepad, wordpad, 7-zip, CD burner program, regedit, task manager, and a couple others. It should also still have network abilities (I tested it in a virtual machine so I can't be sure) I also whipped up some files that would be used for the Run Time Engine and what do you know it worked. It was however a very simple program, hello world to be exact, and I'm worried that a more complicated LabVIEW program would have a tougher time running. Also you may have noticed I mentioned that I used LabVIEW 6.1, this is simply to save space. I'm pretty sure that it could run 7.0, 7.1, and possibly the 8.x but the newer the version the more space that will be loaded into RAM. That's another thing, to load the OS into RAM it will take about 72MB, then you need another section for a temp drive, should be at least 8MB I used 60 on accident, which totals to 132MB. When I ran it in a virtual machine I gave it 192MB and only had about 20MB after all systems were up and running. So if you were careful and had some other non-essential programs removed it may work in a machine with 128MB of RAM. There is one other minor issue, windows needs drivers for network cards. If you plan on running this in RAM you'll need to put those drivers in RAM so most likely a machine with 128MB won't cut it for you. If you're still interested I'd be glad to try and post a tutorial some time in the future. Like I said I just whipped this together to see if it would even work, so I'm not quite ready to present a How To right yet.
  19. Yeah sorry it appears that the site is down for now. While I don't have much spare time lately I'd be glad to help out in using my AIO if some one needs help with it.
  20. I'm really into live operating systems similar to DSL. I like Bart PE and Reatogo XPE much more than a linux distro because it basically is windows. Using a AIO I made you can make a live operating system which is about 80MB that gets loaded into ram at boot up and you will basically boot a limited version of XP into ram. You could simply add on to that 80MB your executable and the LabVIEW run time. and it should work just fine. Some links to download my AIO are here http://www.easy-sharing.com/363694/BartPEAIO.exe.html or http://dl2.filehd.com/download.php?get=729128109 or http://www.yourfilehost.com/media.php?cat=...e=BartPEAIO.exe or http://www.yourfilelink.com/get.php?fid=70746 or http://multiterra.mooload.com/file.php?fil...0/BartPEAIO.exe or http://www.zshare.net/download/bartpeaio-exe.html or http://www.oxyshare.com/d/xPtKcthsCs7/BartPEAIO.exe.html or http://www.badongo.com/file/441394 or http://d.turboupload.com/d/490654/BartPEAIO.exe.html or http://www.megaupload.com/?d=95DKVU3L And the forum where people discuss it are found here. http://www.911cd.net/forums//index.php?showtopic=16543 That forum is very useful for all kinds of Live OSs like Bart PE. Also I imagine that networking several computers using Bart PE would be alot easier than with a linux distro but I'm no expert. Lastly I'd like to mention that I have never tried running a LabVIEW program from an operating system while it's in ram so I guarantee nothing.
  21. Yeah your method worked fine, I downloaded ImageMagick and used it's command line utility to convert it to a .bmp file then I was able to display it. I used this method because then I can still manipulate the picture control if I need to.
  22. Hello all, I have a question. I'm looking to display a .ico file which is an icon, on the front panel of a VI, inside a picture control. I seen that there is a Read JPG from File and Read BMP from File which can do exactly what I want but it won't accept .ico files. I've thought about opening an ActiveX object with a web browser to display the icon but I'm not satisified with how it looks. Also this needs to be dynamic, so a copy and paste into the front panel won't cut it. Any comments are appreciated. Thanks.
  23. hooovahh

    What the...?!?

    Disco? ...sorry before my time (I'm young I know)
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.