Jump to content

jaclaz

Member
  • Posts

    21,294
  • Joined

  • Last visited

  • Days Won

    53
  • Donations

    0.00 USD 
  • Country

    Italy

Everything posted by jaclaz

  1. Hmmm, did you use PEtoUSB: http://gocoding.com/page.php?al=petousb Last time I checked it, it only formatted as FAT16 and thus with a limit of 2 Gb. No, grub4dos should have not any relevance. The only possible difference between a 4 Gb and a 16 Gb may be in the partition type used, a 4 Gb can have both a CHS and a LBA mapped partition, a 16 Gb may only have a LBA one. Save the MBR from both the sticks, use HDHacker (pointing to Physical Drive), compress them in a .zip file and attach the file, I'll have a look at it. Just for the sake of experimenting, can you try the migrate.inf and/or the setupreg.hiv on this new 4 Gb stick? jaclaz
  2. Hmmm, did you use PEtoUSB: http://gocoding.com/page.php?al=petousb Last time I checked it, it only formatted as FAT16 and thus with a limit of 2 Gb. No, grub4dos should have not any relevance. The only possible difference between a 4 Gb and a 16 Gb may be in the partition type used, a 4 Gb can have both a CHS and a LBA mapped partition, a 16 Gb may only have a LBA one. Save the MBR from both the sticks, use HDHacker (pointing to Physical Drive), compress them in a .zip file and attach the file, I'll have a look at it. Just for the sake of experimenting, can you try the migrate.inf and/or the setupreg.hiv on this new 4 Gb stick? jaclaz
  3. Well, there MUST be a reason. The problem is probably in your BartPE, possibly a conflicting plugin or something like that, cannot say. How did you build it? Do you use any "non-base" shell, like XPE or somethng like that? jaclaz
  4. I383? I must have a much later release three versions up , it's I386 for me. jaclaz
  5. @Wimb @ilko_t Why not a SEPARATE Auto-it .script "The8Steps4unattended.exe" ? Can you explain better the problem? jaclaz
  6. Well, no. The idea is that WHILE booting BartPE reads migrate.inf and then loads the key. It has been reported to work by several people, so there must be something "peculiar" with your build. Next try is to add the key to setupreg.hiv. jaclaz
  7. Wimb, maybe you are making it a bit heavier than needed. Noone is forcing people to do anything, if people does not want to use this GUI tool they can use your more featured .cmd. There is a possibility, that you seem not to take into account, that one already has a perfectly lited, tweaked and tuned up source (these steps made with whatever methods) and simply wants to use that source to install it from USB. As I see it, this project is somewhat different from your USB_Multiboot, it is not a GUI translation of it, just a simple, honest, plain, "Install from XP USB" GUI app, it is not intended to compete or replicate the already working, full featured batches. You may notice that most of the (very few) reported problems with your batches were "tracked down" to the user having made a wrong or inappropriate choice among the several possibilities the USB_Multiboot offers, if you remamber I even (frienldy ) once accused you of being caught by "featuritis".... jaclaz
  8. amio, clearly you do have some problems in communicating in English, let's try again . Please post: 1) the actual file you need to modify 2) the batch or script you used to attempt modifying it 3) the file edited by hand as you would like it to have after changes jaclaz
  9. Maybe, just maybe, this can change that behaviour: http://www.plop.at/ http://www.plop.at/en/bootmngrusblog.html jaclaz
  10. Sure, I may have misunderstood that, but I must have misunderstood the whole thread as well. How I would thought this thread would go (condensed): .... How the thread has gone (condensed): No problems though, just wanted to clear my view on the matter. jaclaz
  11. Another one, hidcon.exe: http://www.msfn.org/board/Alternative-To-C...1.html&st=5 jaclaz
  12. The program is Letter Assigner: http://www.v72735.f2s.com/LetAssig/ Can you try retrieving the Vid and Pid of the USB device? I have no idea of what USB tool would work on 9x, SIW: http://www.gtopala.com/ should be able to get those ID's you can also try these ones: http://www.boot-land.net/forums/?showtopic=4661 Don't you have a friend running 2K or XP? jaclaz
  13. @Wai Wai Just to clear things up. You asked a question, I gave you my best answer, citing what I consider a reputable source, Hardware Secrets. Then, once you have read the article where the reasons behind the "rule of thumb" are explained, you are free to simply ignore it or comment it's contents, to trust what is written in it or confute it, but I find ignoring it or classifying it as BS only because it does not contain what you want to hear, to be simply unpolite to me and to the time I spent trying to help you better understand the problem. You weren't able to find a single article about the question, I gave you one. Go and buy your 300W PSU, you'll be happy with it, rest assured. jaclaz
  14. Well, since you did not find any article, WHERE did you quote from? It is a "rule of the thumb" that has it's merits when you look at reliability, efficiency and possible heat peaks of the PSU, of the case, or of the room where the PC is. Additionally, PSU somehow work like big cars, that can, at medium speed, actually burn less fuel than smaller ones. You may want to read this article: http://www.hardwaresecrets.com/article/181 And expecially pages 8 and 9 http://www.hardwaresecrets.com/article/181/8 http://www.hardwaresecrets.com/article/181/9 Very often, besides, it's the initial data that is a bit too high, the use of a calculator to more accurately sum up the amount of power actually needed is strongly advised: http://extreme.outervision.com/psucalculatorlite.jsp you may find out that the requirement to be doubled is less than what you expected. jaclaz
  15. @ldb From the screenshot by herbalist it is clear that his external drive uses a Prolific USB to ATA or USB to SATA controller. Usually the make/model of the controller can be derived from the USB Vid/Pid: http://www.boot-land.net/forums/?showtopic=1659 Once you have the manufacturer and chip, you can try getting the win98 drivers from the manufacturer site, in the case of Prolific: http://www.prolific.com.tw/eng/download.asp If you could post EXACT model of the hard disk it may help too. jaclaz
  16. Hmmm, the fact that the site is registered to godaddy.com from Belarus: http://en.wikipedia.org/wiki/Belarus that the Admin and Technical representative is the same person, with a gmail account, that there is no actual address or telephone number on the site, that the cited "OEM SoftSales Ltd." company appears to be non-existing, that the site is listed here: http://spamtrackers.eu/wiki/index.php?title=Soft_Sales aren't, when put all together, the best clues to answer yourself the question? jaclaz
  17. REG.EXE: http://www.ss64.com/nt/reg.html http://www.robvanderwoude.com/ntregistry.html jaclaz
  18. The usage of "Me" in the same sentence with the verb "to run" is usually considered a (minor) offence, using also the attribute "better" could be judged as a felony. jaclaz
  19. What USE is that machine aimed to? That is the main thing you have to ask yourself when choosing an OS. jaclaz
  20. You are welcome. After all it was easier than what I would have thought. jaclaz
  21. jaclaz

    USB Booting issues

    WHICH MBR's? Did you run MBRFIX? Start again, run the HP formatting utility and post the MBR and bootsector, extracted with hdhacker, after running it. jaclaz
  22. basically a .inf file is an installer script, that adds the relevant keys to the Registry, copies files to system directories, etc. Read this article (.inf files explained in a simple, effective way ): http://www.wd-3.com/archive/InfFiles.htm You have to browse the said .inf files (Notepad will be enough) and check that you have in your system and/or appropriate source the files mentioned in them, optionally you can use this "specific" experimental app: http://www.boot-land.net/forums/?showtopic=3960 then you simply double-click the .inf file. Be warned that it will be a long and prone to errors procedure.... jaclaz
  23. or simply open it in 7-zip.... jaclaz
  24. The "main" related files should be: ptpusb.dll ptpusd.dll ptppusb.inf sti.inf sti.dll stillcam.inf it's a looong shot, but you can try checking all references in said *.inf files and try installing them. Also you can build TWO nlited .iso's, from the same source, one with NO removed items, and one with ONLY the Digital Cameras support removed, and analyze the differences.... jaclaz
  25. FYI, something can be done with 16 bit apps, too : http://www.boot-land.net/forums/?showtopic=5105 jaclaz
×
×
  • Create New...