Jump to content

Nuno Brito

Member
  • Posts

    242
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Portugal

Everything posted by Nuno Brito

  1. Good news!! Judging by the picture I'd say your install is using 109Mb with full sound support and the explorer shell going. That's normal. You will need to do some changes on the windows install before it can run from USB. These changes can be performed manually but they are best done if automated by PEtoUSB - have you managed to get the drive recognized? -------- You can also forget about the ISO file for the moment as it won't be necessary for the USB boot, what you need are the target project files that were used to build the ISO. Open explorer at your computer and look inside the winbuilder folder. Inside you should find a folder called "Target" - that's the folder that you point at PEtoUSB as source of the files that will be copied over to the pendisk. This is the easiest way to get things done.
  2. You should have read the previous topics. We are talking about creating a XP OS running from a 128Mb pendisk with sound support. You suggest that nLite will produce a 90Mb ISO but these are the installation files for windows and we need a running Windows XP, do you understand the difference?
  3. In this case I would then suggest you to get some reading glasses because I didn't wrote such thing and I'm a longtime windows software developer.http://nunobrito.eu/download.php?list.4 Even for my professional case, I don't really have much need of using Windows specific software nowadays so I opt for free software projects that are platform agnostic and use WINE mostly to try out things that were made only for the Windows platform. Wrong assumption, the car isn't broken at all and I drive it safely around the big city all day long for free without fear of being robbed.. --------------- The explanation for the reason why windows based malware doesn't work is mostly due to the reason that they often stomp when trying to infect ctfmon.exe, winlogon or any other critical portion of Windows only to find them missing.. Found a similar blog post here that writes in more detail about this sort of experiments --> http://jadmadi.net/blog/2005/01/27/linux-w...uses-with-wine/
  4. This isn't very usual.. Don't worry about the filesystem being FAT16 or anything else, the tool will help formatting. I'd try using another computer as some viruses often intercept this sort of things. Also, you can try a tool called HP USB Storage - http://files.extremeoverclocking.com/file.php?f=197 that should be enough to make your pendisk bootable. However, you will still need the PEtoUSB tool to prepare the OS for being booted from the USB drive. One idea to bypass the annoyance that you're experiencing would be formatting a second drive and then just copy the OS files from one pendisk to another, guess you can quickly find someone to borrow a pendisk or even get another one as you say. But beware that pendisks above 2Gb aren't well digested by PEtoUSB tool. ----------------------------- Well.. BartPE is old and packed with a lot of bloat by default. Comparing it to NaughtyPE or any newer project is a bit like thinking about the Ice Age of PE boot disks: http://www.boot-land.net/forums/index.php?showtopic=6616 If you look closely at how bartPE works, it will blindly follow the guidelines of txtsetup.sif and copy everything over to the target location without caring if the files are needed or not. Some years ago, I've even made a small tool that slimmed bartPE down from 220Mb to 36Mb while keeping the drivers and a command line - http://nunobrito.eu/download.php?view.2 ------------- These new techniques you find today are the state of the art on this field and have grown so advanced to a point where it is possible to automate the build of a barebone XP ISO sized in 31Mb that would use the full explorer shell. NaughtyPE is based on the NativeEx project which by default builds XP PE OS's at ~50Mb. ----------------------- How to reduce below the 128Mb size limit with full sound support? To reduce the size of your NaughtyPE, simply enable the autoUPX script at the "Finish"-->"Optimizations" subfolder inside the project window. This should slim down about 40% in overall size but will consume more memory, at least 380Mb of RAM are advised when running these OS's with full UPX compression. In alternative, try disabling some of the freeware programs that come included by default inside the OS as they also take up some considerable space.
  5. I'd say play on the safe side and ignore tutorials for other projects. All you need to do is follow the instructions inside each project that I've mentioned before. For NaughtyPE for example. - You will need the Windows XP source files somewhere on disk - Download and unpack NaughtyPE and run winbuilder.exe - There's a tab called Paths - click and select the path where your XP source files are placed. - Click the Play button (big blue button) This should provide you a good boot disk below the 100Mb. To make a bootable USB pendisk I'd recommend this nifty tool from codebeetle: http://gocoding.com/page.php?al=petousb It was made with bartPE in mind but it should be compatible with NaughtyPE too. ------------------------ You don't need nlite for anything, these projects are best used with full XP sources to ensure that all files are present to copy the necessary files. VistaPE is also simple to use but it doesn't come (yet) with full sound support and it is a bit slower and bulkier to load, so I really recommend going with XP for this purpose.
  6. Type warez on google or tryout kazaa to find some executables for your favorite programs, this should be fun. Whenever I get bored, I double click on one of those false images types that are in fact executables to see what they do. But since I'm running Wine at Ubuntu, they never seem to breakthrough..
  7. LiveXP is a good option but if you want audio support I'd recommend trying out naughtyPE. You can go as low as 31Mb for a running XP OS with the Explorer shell. Take your pick, both projects are legal and available here: http://winbuilder.net/download.php?list.5 Good luck!
  8. Hi Jennifer, very true indeed! Happy new year too!
  9. Hi, Please retry again. Also, beware that the present version is not translating correctly the entries for the newest WPI. This should be solved soon.
  10. Windows PE versions previous to 2.x are available only to properly licensed OEM vendors. You might want to contact Microsoft about this matter to know if they authorize your use or not.
  11. You should look for help at the VistaPE forums at http://boot-land.net
  12. I had already read these news some time ago, at the time I went to the OS site to read more about it but didn't caught much more of my attention. Yes, today's bug and solved within hours.. http://ubuntuforums.org/showthread.php?p=6385463 It seems to occur when you have a set of definitions made previously for a specific NIC and network manager will use them while ignoring the one that is real and active on the system. The OS remains independent from this bug in the UI tool which can be solved today by using another tool as you mentioned or wait for the next update (hasn't it been fixed yet already?). On my work machine I use two NIC for different networks (office & internet) and didn't noticed any differences with all updates installed, things kept working as expected. No need to worry about WGA to keep my system up to date.
  13. Sorry. I am moving all websites to a dedicated server with better conditions. This transfer should take approximately one~two days to get everything back to normal. Please visit this topic later tonight to check how things are going.
  14. Happy 5th birthday!! Still think it is the very best way to install windows software, ever!
  15. You're certainly exaggerating otherwise I'd interpret your comment as a plain malicious or perhaps as an ignorant remark from someone who isn't aware that web development starts with simple steps that are taken at first with simple text editor before moving to full featured IDE's. I think my previous comment was quite clear: I gave a few tips regarding how to set up a web development environment using simple open source tools. If you have any doubts regarding anything I mentioned before, please google for answers and I will also be available to explain whichever doubts you have but please be a bit more specific than "you should really clarify what you are talking about" ----- How will dreamweaver help when all you need is a simple site with the least code possible, or how would people without basic html/php/css/javacript skills figure out how to solve the cross-browser woes that differ from IE to other browsers? This Dreamweaver compare is almost like saying that GIMP is simply the best image tool possible - but what is the use of a tool to which you don't take full advantage nor understand it's features/disadvantages? Then you would complain that your site is sluggish to load, you'd be sad if only IE users could view it correctly and that it won't be easy to find a template available on the web that fully matches what you wanted in the first place after hours googling for some kind soul that would make it available for you. ---- It's not a nightmare to manage several sites with other tools, many people have been doing since the beginning of the Internet and everyone has the right to choose their tools. For instance, I use ssh to remotely connect to the web server and directly edit the pages without need for FTP transfer or any additional steps, this edit process can also be done from any machine without need to install dreamweaver or anything else. There are plenty of things regarding site administration that go beyond the simple looks and functionality. You also need to take into account the search engine optimization, the site performance, learn how to make pages capable of surviving spam bot slurps, DDoS and all sort of things to which a site is vulnerable once it goes public - does dreamweaver also comes with a plugin for these? --- You're entitled to your opinion but flaming the perspectives from other members doesn't make your perspective right and almost resembles some school-age reasoning.
  16. As was mentioned before, you only need the Windows Vista Install DVD. You can build your VistaPE with the Vista Install DVD to get explorer and other Vista specific features working, no need for WAIK on this case.
  17. One feature about scripts is that you can include binary files inside them. These files are encoded inside the text in a similar fashion to how an email message contains file attachments. Totally free. Look on the screenshots, they show windows explorer. With windowblinds it looks even cooler. If you're using the WAIK from MS instead of the Vista DVD install folder then you don't get the windows explorer because WAIK doesn't has the needed files. If your boot disk doesn't start with explorer - look on the scripts and look on the available settings, maybe something needs being selected right - by default it will use the explorer shell when you use the project for the first time without changing nothing.
  18. Sort of. Depending on the features you need, the complexity is variable so I'd say that you *can* "make everything happen" but sometimes it takes too much work to do it by hand - especially if you need to repeat the process one day. In most cases yes. In particular situations you can only add some registry settings when the system is booting, these are designated RegAddBoot on the scripts. I'm not the author of VistaPE, I just keep track of their developments. On this case, all files are assembled on a external folder and then packed into a new wim file when every all other build steps are concluded. Imagine it a bit like building a lego house from scratch. Besides being time consuming you'd be left with more time consuming tasks trying to figure why "x" feature doesn't work or how to get the "Classic" start menu or some other details. This is the reason why we've scripted it in the first place - to avoid making the changes manually, especially when you're perfecting the boot disk image. From my experience, I'd recommend that you first try the automated tools and only then start working on manual customization to learn from what is being done specifically with your chosen settings and windows install source. It will save you time to get an initial boot disk image with the scripts. You can later use the resulting image to customize it manually.
  19. No. You are likely building "your" Windows PE 2.x from the WAIK alone and you will need the Vista Install files to add features like IE and Explorer that don't come available by default on the WAIK as you might imagine.. You can use the WAIK but then you wouldn't have explorer or IE unless you added them manually by yourself as described above. The simplest possible way to get everything you need in a automated fashion is to simply use VistaPE as intended with a Windows Vista install DVD that will do all these tasks for you.
  20. It's easy to start, look on the project site, there's a quick guide: http://www.vistape.net/vistape-quickstart.htmlYou can get the full VistaPE project from the download center inside winbuilder.exe I recommend that you first try the "base" VistaPE that doesn't come with too many features and then download more from the download center as you get more comfortable working with wb and ensure that you always get a working build. If you have more doubts then you're welcome to place on the respective VistaPE forum where myself or other folks can help to explain these things.
  21. Why do you want to have all that hard work on your own? Explorer, MMC, IE and many other features like WIFI and such have all been scripted. If you need a guide - read the scripts. If you don't understand the scripts then I'm afraid that a guide wouldn't help you much as you'd still need a lot previous experience debugging these sort of boot disks to avoid hardcoded paths and understand where things can go wrong - are you sure that this is what you want?
  22. Run VistaPE and you get an working explorer/IE solution from WinPE 2.x If you want to do it manually, look on the code of scripts that compose VistaPE and you can add the changes manually by yourself as was mentioned by yaleyu. Personally, I think that the automated way will save a lot more time and troubles. There are a lot of tutorials available out there for VistaPE, you can google or look on the site for more quick-start info - it's only a matter of downloading the project and pointing it to the place where your DVD files are placed anyways.
  23. Yes, that describes very well the situation I experienced I will try other themes, in 8.04 I wasn't using the human theme but rather a XP zune theme that looked really good. Thanks.
  24. I like 8.10 - the only troubles were related to compiz where the 8.04 worked very well and now from time to time the top of the window seems to glitch a bit. 8.10 brings a tabbed gnome a bit like firefox does and native support the Huawei 3G USB connect card from Vodafone and other communications operators. Last but not least, it comes with tool for creating USB bootable pendisks to install Ubuntu from USB drives.
  25. You did good, it turned out that the author already added IE 7 as default on his project. I hadn't noticed this yet, thanks.
×
×
  • Create New...