Jump to content

crashfly

Members
  • Posts

    405
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by crashfly

  1. Ok. It appears I have lame hardware. At least I know that now. Nothing caused by WinToolkit. It is just an odd DVD burner that likes to do stupid stuff. All is well now.

    I installed from a USB drive and everything works as it should. DVD burner just being bad. Probably need a new one.

  2. I seem to be having a reoccuring error when building an install image with the latestest WinToolkit (build 65).

    "Windows cannot install required files. Makre sure all files required for installation are available and restart installation. Error code: 0x8007048F"

    Anyone have any ideas what "update could be causing this error, or is this just another bug with the latest WinToolkit?

    If anyone cares, I have included my last three option presets. All three give the same error.

  3. Likely your issue is related to "running out of space". WinToolkit makes a mount of the wim files (by default) to your system drive. Typically your system drive is also the location of the temporary directory. Both of those together could have caused your system drive to get full and therefore causing odd problems with your other programs (I have seen it happen when a drive gets full). The big lesson here is to make sure you have *lots* of room free on the drive that WinToolKit uses for its work.

  4. To add further information on this discussion, most if not all of your hdd storage providers have the following note attached to the technical specifications of their hdds (this quote was from Toshiba's website):

    One Gigabyte (1GB) means 109 = 1,000,000,000 bytes and one Terabyte (TB) means 1012 = 1,000,000,000,000 bytes using powers of 10. A computer operating system, however, reports storage capacity using powers of 2 for the definition of 1GB = 230 = 1,073,741,824 bytes and 1TB = 240 = 1,099,511,627,776 bytes, and therefore shows less storage capacity. Available storage capacity (including examples of various media files) will vary based on file size, formatting, settings, software and operating system, such as Microsoft Operating System and/or pre-installed software applications, or media content. Actual formatted capacity may vary
  5. There seems to be a bug when following the "View New Content" link at the top right of the webpages. I get 54 pages of all content. The only good thing about this seems to be that on the first couple of pages are "highlighted" as if they were new posts, while there is still additional read posts that fill the rest of the pages.

  6. 1. I wish you could have 1/4 button and 3/4 text but it doesn't work like that, unless i go through the annoying work of making my own buttons.

    Technically you can (easily), but only if you programmed using the Qt IDE. But that is another discussion. ;)

  7. LOL I guess I'm showing my age.

    Don't feel bad about that. I learned what the "original" definition of Gigabyte was before the storage companies decided to change it. That is why I still answer 1 GB = 1024 MB. Say what you will about the storage companies that changed the definition, I will stick with what I learned. ;)

  8. The big hoot is that now that Microsoft has reviewed my software and agreed to replace it, they say: "Please allow 4-6 weeks for delivery of your complimentary kit." What a company.

    The fact that you had to go through the whole process is still "criminal" to me. Best of luck to your future MS endeavors.

  9. I can't believe everyone is wrong so far :P You won't believe me but the answer is actually 1000MB

    It depends on who defines what the Gigabyte and Megabyte are. In basic computer science technical terms, a Gigabyte is equal to 1073741824 bytes (1024^3) or 1048576 kilobytes (1024^2) or 1024 megabytes (check google's caculation on that). So depending on what you consider is a real byte, I consider 1024 to be correct in computer science terms. Most storage companies actually have changed to the "1000" number in order to less confuse customers. Storage companies did that, even though those numbers are incorrect.

  10. While I agree "cracking" software without paying for it is bad, in ways it does make some people who "crack" those games more likely to purchase the game legally. Take for instance those people who regularly "download" games without paying for them. Those people do not pay for those games, so the legal "grey" area is that they would have never paid for the game anyway. Some of those people like the game well enough to come back and pay for it. Yes, the argument is not etirely 'strong', but the hacking underground will happen no matter what companies do. Make the game good enough, people will pay for good products, despite what hacking has been done.

  11. be careful, you don't want to break any rules now :P

    Off Topic: As if MS never "broke" any rules when its company was getting started ... I never had to activate MS-DOS or even Windows 95 to make them run. They just worked. MS treats its customers nearly as if they were criminals these days. I paid for it legally. It does not mean I want to deal with their crap activation.

  12. Sorry i haven't been on much in the past couple of days, went home to visit my parents for 2-3 days.

    Also i had to take my laptop apart to clean it as it was overheating and shut itself down whilst playing Sniper Elite V2, its idle temp was 79C and under load could burn my hand.

    Anyways now that's cleaned it's now operating at 45C idle and 75C when playing Sniper Elite so a big improvement :D

    Hey, no need to apologize to us. You do this programming because that is a *hobby* to you. We thank you for what time you *do* give us. Thank you very much. Carry on at your earliest conveinence.

  13. ... I've had valid copies of Windows 7 and Office 2010 placed on the banned list and have had to ship them copies of the software (at my expense) and go through weeks of down time until they reach a verdict. Anyway, if somebody can find out how often "frequently" is please let me know so I can avoid this hassle and just install a reimaged drive, instead.

    Really? Hmmmm ... makes me want to just hack the activation instead. That seems a bit harsh. I guess the flip side to that would be to just pay for an MSDN license in which you would get a bunch of keys with I think up to 10 activations on them. (or course one could back up your activation if your computer did not change its hardware, but that is all a seperate topic) ...

  14. Appearantly, the "McRip" update server is active. However, due to a broken setup I have with IPv6, WinToolkit was trying to connect over IPv6 and not IPv4. Disabled IPv6 (at least temporarily) and everything started working. I know I have a borked IPv6 implementation. I am working on fixing that. I did not realize it was going to be an issue with WinToolkit.

    Still, there are no direct links for the "McRip" update catalog.

    @Legolash2o - Secondly (as a possible selection), it may be a good idea to implement a check for both IPv6 connectivity and IPv4 connectivity (or at least the choice if IPv6 does not work).

  15. I am not a new person when it comes to using WinToolkit (using v.1.4.0.32). However I am having some difficulties with trying to locate the updates to use with WinToolkit.

    Currently the error message I get when pressing the "Update Catalog" button is:

    Neither McRip or SoLoR Update servers seem to be active. This error will also occur if you have no internet connection or if you are behind a proxy server.

    I do have an active internet connection and I am not behind a proxy. Also, I have searched the forum and have been unable to find the links to get directly to the "McRip" updates or even the "SoLoR" updates.

    Anyone got any ideas?

  16. A dual/multi-boot setup would be best - for comparison.

    One better would be to use a virtual machine. As a developer, you probably should have several anyway just so you do not mess up your production machine. That is likely what I would do if I had any interest in Windows 8. Right now, not so much.

  17. *Edit:

    However, we can see that the two passes are executed anyway even if processing amd64 first and x86 second installing Windows 7 64-bit versions!

    There is a way around the "two pass" problem. Put in a statement that tests for a file that is created the first time the batch file is run. If the file is there (test returns true), then exit the batch file.

    Simply put this at the beginning of the batch file and problem is solved. No more "run twice" problem.


    if exits=%SystemDrive%\filetemp.txt exit
    echo . > %SystemDrive%\filetemp.txt

×
×
  • Create New...