jaclaz

Actually, and with all due respect , the issue is not as much with the pokemonspeak, but with the actual Polish... Can you translate "prestidigitator"? jaclaz Polish source courtesy of: http://www.uebersetzung.at/twister/pl.htm Item #39_ http://www.uebersetzung.at/twister/pl.htm#T102475

Yep, HP bought 3com a few years ago. Yes, AFAICT the given link on gateway is the appropriate driver. You can however try the fe575cx.exe file here: http://www.ictcompany.com/store/support_download.php http://www.ictcompany.com/Drivers/3ccfe575bt/fe575cx.exe You can also check if among the drivers you have in the "Windows" list (scrolling down) there is one for the 3C575 . You can check on the old 3Com page how the drivers are for "series" of cards: http://web.archive.org/web/20050312092813/http://www.3com.com/products/en_US/prodlist.jsp?tab=cat&pathtype=download&cat=10&selcat=PC+Cards&family=68 http://web.archive.org/web/20040817075252/http://www.3com.com/products/en_US/result.jsp?selected=all&sku=3C3FE575CT&sort=effdt&order=desc It seems ike latest is fe575291.exe, that you can probably get from here: http://www.filewatcher.com/m/fe575291.exe.738816.0.0.html jaclaz

No prob, everyone has been a beginner at least once and at somethng . The good news is that the 3Com card is working (in the sense that is detected correctly by Windows 98). So you need to find the drivers for it (and since the only working media you have is the CD-ROM you will have to put them on a CD-rom), or has it a floppy drive? Check the physical card for any number, the one you posted a link on e-bay is NOT the same as the picture you just posted (this latter seems a CARD BUS card, see the golden strip, which is more likely since the card is detected as being PCI) Check if the one you have is like this one: http://www.ebay.com/itm/3COM-3CCFE575BT-D-Dell-Fast-Ethernet-10-100-Base-TX-PC-Card-PCMCIA-/190716341606?pt=US_Laptop_Modem_Cards&hash=item2c67946d66 IF it is this one, the driver should be this one: http://support.gateway.com/support/drivers/getfile.asp?id=13664&dscr=3com%20megahertz%2010/100%20lan%20cardbus%20pc%20card%20(3ccfe575bt)%20driver&uid=354825832 jaclaz

Yep, JFYI: http://www.businessinsider.com/new-avis-logo-looks-just-like-apples-and-microsofts-and-dozens-of-other-sans-serif-brands-2012-9 http://www.webdesignerdepot.com/2009/03/40-excellent-logos-created-with-helvetica/ The future is seemingly sans-serif (and with not that much intelligence too ) jaclaz

Sure, as long as you don't give commands but just test changing access levels you won't do any harm. Yes/No. http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html Meaning: Do all disks have an updatable firmware (actually a mini-os)? Yes/No. Do all modern disks (please define modern) have an updatable firmware (actually a mini-os)? Yes. Is this firmware available? Yes/No. Do all disks connect through a TTL? Yes/No. Even if all disks would connect through TTL, do we know how exactly? No. If you prefer, why do you think that the good guys at Acelab: http://www.acelaboratory.com/ manage to successfully sell a piece of hardware (that could be valued at the most 500 bucks) together with some software of theirs for 5 thousand bucks or more (+ something like 2 grands/year per license) ? jaclaz

Yes/no. Whatever is in folders with a tilde in the name won't be there anymore after the install is finished, so if you want to (say) later add an optional component you have not the source anymore. If I recall correctly the /noreboot means that it won't automalically reboot but instead will ask you to reboot (of course if you answer "yes" it is pointless ). jaclaz

pr0B1Om? You mean pr0B13/\/\! (watch your spelling) \/\/|-|@7 pR0B13/\/\? http://www.imdb.com/title/tt0072431/quotes?qt=qt0484668 jaclaz

Start by describing (briefly) your current network setup. (which hardware you have and more than that which subnet and subnet mask are you using). Most "standard" devices (I am talking of DSL modem/routers) tend to use: 192.168.1.1 255.255.255.0 The built-in DHCP server (if any) will then normally assign addresses in the range 192.168.1.2 up to 192.168.1.254. Simply open a command prompt in one of the other computers you have connected to your network and in it type: ipconfig /all and press [ENTER] it will give the address of that machine and the subnet mask (besides the address of the gateway, i.e. your modem/router). If you have (say) 5 PC's in your network and the address of the one you check the DHCP assigned IP is (say) 192.168.1.18 try assigning that IP + or - 5+1=6, i.e. 192.168.1.12 or 192.168.1.24 to that Dell laptop. (this way we are relatively sure that there is no duplicate IP on the network). Then, simply try PINGing the gateway and/or the other computer of which you know the address from the Dell laptop. Sorry I don't understand what you mean, you need to provide more details... jaclaz

Start doing the standard checks, remember that that Dell PCMCIA card is 10 base-T, whilst your network is most probably a 100 Base-T, you have to check if the setting in your Router/Modem/whatever are set to "auto" or you have to manually set them to 10 base-T. IMHO it would be easier if you would configure manually the TCP/IP address and subnet instead of relying to the DHCP you have (IF you have one). Go here: http://www.windowsnetworking.com/articles_tutorials/Windows_9598ME/ and check the relevant tutorials, usually if there is an issue with networking, the solution can be found there. Start from this one: http://www.windowsnetworking.com/articles_tutorials/win98.html jaclaz

Rednecked: http://rinkworks.com/dialect/ You is right mah friend mah bad. But the actual nice part is to have submix8c write Cockney ,): http://www.rinkworks.com/dialect/dialectp.cgi?dialect=cockney&url=http%3A%2F%2Fwww.msfn.org%2Fboard%2Ftopic%2F158422-how-to-make-windows-xp-pro-sp3-preactivated-cd-with-own-oem-info-for-all-major-brand-or-provider%2Fpage__st__11 jaclaz

Let me understand, if I get it right you have THREE "subsystems" that are not working properly: PCMCIA+Wireless Network USB Wired Network listed in order of DEcreasing difficulty to solve. If I were you I would FORGET (temporarily) the PCMCIA + Wireless and the USB, and try to have the wired network working, then with that working solve the USB issue and with the USB working troubleshoot the PCMCIA (it is not entirely impossible that actually a conflict of some kind exists between USB and PCMCIA). BUT is this the machine? http://support.ap.dell.com/support/edocs/systems/pmac2cm/en/en_ug/specs.htm it seems like it has not a network card (wired). Can you clarify/explain/expand? BTW, JFYI - and to be picky - it is not about "proper" PCMCIA, but rather about CardBus jaclaz

I guess we are mixing two or three different approaches. If you use the USB you need NOT any support for the PCIe card, once the system WITHOUT the PCIe card is installed and working, then you add to it the card and relative drivers. Right now you installed in IDE mode and you need to switch to AHCI mode. This is doable, but is not as simple as you thought. The approach is sketched here: http://forums.pcper.com/showthread.php?t=444831 Or, if you have a working PE of some kind, you could inject the mass storage drivers to the offline system. http://www.911cd.net/forums//index.php?showtopic=22523 Still IMHO both the latter approaches are more complex than plainly installing from USB (directly in AHCI mode). jaclaz

Yes. My memory is obviously fading, but apart from the BOOT.INI submix8c pointed out, but it is possible that the actual loader used in this stage is not NTLDR (in the sense of the "real" NTLDR but a SETUPLDR.BIN renamed), I seem to remember that a \I386 is created. If not, a good idea, expecially if you are going to image the disk and re-use it, it would be to copy anyway the whole \I386 to the disk. jaclaz

You maust have either some missing file or anyway something setup incorrectly. WINNT32 has worked on *any* machine, with*any* NT OS since the dawn of time. About MBRFIX it looks more like you have something preventing direct disk access (or the like). For the MBRFIX besides finding the actual issue, there are workarounds, one is to leave the normal bootsector invoking NTLDR "as is", add a line to BOOT:INI pointing to grub4dos and add grldr to the root, then use grldr to load the IO.SYS: For WINNT32, try running it as follows /(we are talking of 2K, right?), this will install the Recovery COnsole: Winnt32.exe /cmdcons If it works, then try with: Winnt32.exe /checkupgradeonly Them try runnign it with the usual tools, procmon, regmon. filemon, etc., try tracing it with deppends.exe, etc. Or, even more simply, since you are testing new 2k installs, make a new 2K install and try running wiint32 from this install. jaclaz

You must have missed this before buying that (whatever it is) batch "compiler": http://www.robvanderwoude.com/scriptcompilers.php jaclaz

No real changes AFAIK, the above should work with WIndows 8 allright. See also: http://reboot.pro/16544/page__st__50#entry151250 http://blog.concurrency.com/infrastructure/dual-boot-windows-8-from-vhd-using-windows-setup/ jaclaz

Hmmm , no. Examples: j00Z /\/\U$7 b3 j0|<1|\|9 L337 $P34|< 1$ /\/\(U|-| b3773r 7|-|4|\| r4|\|D0/\/\ (4P174L1Z4710|\| yoU MUsT bE jOKiNg LEet sPEAK iS much BETTeR ThaN raNdom cAPItalIzatIoN. @submix8c (the previous examples were of txt lingo, NOT l337) jaclaz The present post was made through: http://www.brenz.net/services/l337Maker.asp http://textmechanic.com/Letter-Case-Converter.html

See if you can find anythng of use here: http://www.911cd.net/forums//index.php?showtopic=16713 If you mean "directly" preparing the target disk from a booted Windows machine, sure what is the problem? Just partition/format "normally", then run MBRFIX to change the bootsector of the active parittion to the one invoking the DOS IO.SYS: http://www.sysint.no/nedlasting/mbrfix.htm Remember that for DOS 6.22 and earlier you will need to have IO.SYS as the FIRST file in the filesystem (i.e. copy to the newly formatted volume IO.SYS, MS-DOS.SYS and COMMAND.COM in this order). On the other hand, you could make a "ready to boot" install disk, using the appropriate WINNT32 switches, like /syspart:C: /tempdrive:C: /makelocalsource /noreboot. http://technet.microsoft.com/en-us/library/cc940493.aspx jaclaz

LOL missed that one, thanks Jorge; "NCI" is certainly going to stick with me! The real issue being, as said: that unfortunately the acronym has been neededly shortened, so it fails to deliver fully the message..... On the other hand, an alternative name, short for Modern Enhanced Revolutionary Dumb Approach , while still predating from the Italian language, would not be fully appreciated by the non-italian speaking peeps. jaclaz

You need a newline: This snippet assumes that a filetype "java.Document" already exists (and is associated to the .java extension) jaclaz

Try these: http://blogs.technet.com/b/heyscriptingguy/archive/2009/03/27/quick-hits-friday-the-scripting-guys-respond-to-a-bunch-of-questions-03-27-09.aspx ListFileAssociations.vbs Set objShell = WScript.CreateObject("WScript.Shell")objShell.Run("%comspec% /K Assoc | more"), 1, True ChangeFileAssociation.vbs Set objShell = WScript.CreateObject("WScript.Shell")objShell.Run("%comspec% /K ftype TIFImage.Document =""C:\Program Files\MSPVIEW.exe"" ""%1"""), 1, True Afaik, a file association has a number of related keys in HKEY_CLASSES_ROOT (that the built-in commands know how to manage). The snippet you posted most probably originated (without credits) from here: http://jimkeller.blogspot.it/2005/09/changing-file-associations-in-windows.html Which BTW "justifies" the otherwise senseless: If you hardcoded .java, there is no need to check if the first character is a dot.... This might be useful to quickly check associations: http://www.nirsoft.net/utils/file_types_manager.html jaclaz

Where did you get that snippet? Particularly, where did you get the Registry path? Any reason NOT to use the ASSOC/FTYPE/ASSOCIATE commands? http://ss64.com/nt/assoc.html http://ss64.com/nt/ftype.html http://ss64.com/nt/associate.html jaclaz

Sure m8, AAMOF twas mor intentional thN un4tn8, we normaly try 2 uz en 2 comnC8 on dis board. Moreovr we'd aprec8 havN mor Dtails, uno lk: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html bt: No. (u cnot). n/a sry 4t answers nt benefitting u jaclaz (translations courtesy of: http://www.lingo2word.com/translate.php)

Good , though it seems to me like what you did is more like throwing yourself into a mud pond (dressed). Let's see if we can help. The tutorial #30 on RMPREPUSB site is about using a F6 floppy with the drivers (text mode). If you don't have them, (if I get it right) it won't be of use. The WinsetupfromUSB instead is about having the appropriate drivers integrated. Somethng got "wrong" (from the screenshots you posted) with the actual USB stick formatting or your BIOS somehow re-mapped in a strange manner the device/images. Start again with WinSetpFromUSB. Using it you should use RMPREPUSB to ONLY format the USB stick (WinsetupFromUSB should do all the rest). This is most probably part of the issue: BUT, do another thing (test to see how the thingy behaves). Open RMPREPUSB. Choose: Partition Size: Max Bootloader options: XP/BartPE bootable (NTLDR) Filesystem and Overrides: NTFS (or FAT32) and Boot as HDD (C: 2 Ptns) And "prepare" drive. Now, open the drive in Explorer, and copy to it: NTLDR (copy from *any* XP you have available) grldr (get it among the already downloaded files or directly from http://code.google.com/p/grub4dos-chenall/downloads/list ) a file BOOT.INI (created with Notepad or other text editor) with these contents (you can copy and paste): [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect C:\grldr="Grub4Dos" Try booting from the stick on the machine. You should be able to get to the boot .ini choices. Choose the "Grub4Dos" entry. You should arrive to a grub> prompt. In it, type: root ( and press the [TAB] key. You should see a list similar to: Type: root [ENTER] you should get (hd0). Type: [ENTER] you should see listed of the files on the stick: ntldr, boot.ini, grldr. If everything is like described, reboot normally, delete the files from the USB stick, and run again WinSetupFromUSB (the stick is already OK and you need not to re-format it or use again RMPREPUSB). Post if anything is different. jaclaz

Sure, I know , I was just trying to have you make a quick laugh and cool down, it's simply not worth it to get mad at people .... jaclaz