diamant

No; should I do so? I have partially good news: 1.) Blinking cursor - solved . 2.) But now new: I call it ... "34-minutes-error" :angrym: . See below. 1.) The solution of the problem with blinking cursor seemed to be to start the WinXP setup directly from internal HDD. I started at first smartdrv c+ (this increases copying speed drastically). And then I went to the I386 folder (which I had copied on internal HDD), and ececuted winnt. And now I got to the "next" screen in the WinXP setup after blinking cursor! I.e. the blinking cursor appeared still, but remained only for about 1 minute - and then I could continue setup . So this problem remained no longer, but I'm now coming to... 2.) After the first reboot during setup I can choose "WinXP setup" (or similar) from the (automatically installed) WinXP boot manager. The setup came up to the point where devices(?) are installed. But at this point the setup froze (also the blinking green lights down right on screen)! The setup says that there are 34 minutes remainung. I waited about more than 1 hour; nothing happened. You can see the frozen screen: Another update: I has now an effect if I change BIOS setting from IDE to SATA/AHCI (or vice versa). I tried changing only once; after first appearance of the 34-minutes-error I rebooted with SATA/AHCI-mode for testing. With IDE-Mode I get up to the point with the 34-minutes-error. With SATA/AHCI-mode I get the well-known bluescreen directly after selecting "WinXP Setup" in the WinXP bootmanager. So I think I should use IDE-mode for further tries. Could the 34-minute-error have something to do with nLite? I used ist again before copying the WinXP setup files to the Acer's internal HDD. But this time without creating an ISO file, but only "edited" the WinXP setup folder with nLite. I not included the AHCI_Intel_8.8.0.1009_XPx86XPx64_A.zip driver until now, because it seems not to be a textmode-driver (see the *.zip archive)?!

The additional problem which I had was the fact, that the Acer was not able to boot from its internal HDD. I could start 'format D: /Q/S' from the USB-Stick C:, that means on D: there were the 3 needed DOS-files io.sys, msdos.sys, command.com. But after that the internal HDD was not able to boot (with unplugged USB Stick). I always got "no bootable device - insert boot disk and press any key". So it was necessary to use a program like Ranish partition manager: - to set the MBR (master boot record) of the internal HDD from somewhat like "undefined" to "Standard IPL" - to set the Boot flag to "active", That was not possible with fdisk and/or format. Only after that executing 'format D: /Q/S' showed an effect. I tried also this newer version. By using it I got not the described bluescreen, but instead a blackscreen with blinking cursor in the left. It seemed that meanwhile was loaded some setup data(?) in background, but I waited for ca. 30 minutes, and nothing happened. That means: The difference between v.1.0beta7 and 1.4 is only the colour of the screen when stopping WinXP setup... Or maybe I simply had to wait a little bit longer than 30 minutes...? The user littlebigman on http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html had also set the BIOS setting to "IDE compatibility mode", with also no effect. Maybe the BIOS is broken by design. User littlebigman wrote furthermore that he integrated the said Acer's AHCI Intel SATA AHCI Driver (8.8.0.1009) with nLite[#], and had to set in BIOS the "IDE compatibility mode". [#]No idea how he integrated driver; maybe I integrated them wrong?! Tomorrow I can make a first try to install WinXP from the internal HDD by the method to start winnt.exe directly from I386 folder (on internal HDD). Until now: No, it has no effect. See also (as said) the link http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html. The user there had a similar problem.

Here ist the whole bluescreen when using WinSetupFromUSB_1-0-beta7: I downloaded them directly from Acer, finding the drivers by typing the serial number of the 3810T. The guy at the link I've already posted http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html used obviously the same drivers?! I read some of the links you posted; I think maybe there's somewhere the solution for my problem. Problem is that it's impossible(?) to find out the exact information about chipset from that Acer Aspire 3810T-354G32N because system analyzing tools won't run in MS-DOS. Of course I can not exclude that de HDD itself is (physically) damaged in any way. The reason for reinstalling ist/was malware; the previous OS (WinVista) was heavily infected. I recommended the user to use WinXP; he has no WinVista CD or USB-Stick. But I have another new information: I have accomplished it to install MS-DOS on the Acer! Here the instructions (i.e. my way to proceed this): 1.) Create a bootbable USB-stick with MS-DOS. You can use any tool for that; I recommend HPUSBFW_v2.2.3.exe. 2.) Download Ranish Partition Manager v2.40 and unpack it onto the USB-Stick. You'll find a DOS-program part.exe. 4.) Copy the DOS-files format.com, xcopy.exe, xcopy32.exe, xcopy32.mod on USB-Stick. 3.) Boot the Acer from USB-stick. 4.) Start part. In the following screen (from Ranish Partition Manager) select Harddisk 2 (the internal HDD), delete all partitions on it, set the MBR to "Standard IPL", create a new partition, format it (it can be done in Ranish Partition Manager), and (important!) set the Boot flag for the new partition. Save the new settings with F2. Exit now Ranish partition manager. 5.) Start format D:/Q/S. Here is D: the internal HDD, Q means "quick format", S is for installing MS-DOS files (from USB-Stick, which should be actually C:) to D:. 6.) Unplug the USB-Stick. 7.) Restart the Acer and set boot settings in BIOS to HDD. It shoult now boot MS-DOS from the internal HDD, which is now C:. I think this could be a possible basis for installing WinXP directly from the internal HDD?! I could copy all WinXP install files to the internal HDD, boot from HDD and try to start the setup directly from it. If this fails, so I can say that the problem is not the fact that I try to install from USB?!

I try to install WinXP on a Notebook "Acer Aspire 3810T-354G32N". By trying this I get only trouble . Problem 1: The Acer doesn't have a floppy- or CD-ROM-drive, which makes booting difficulty. I can only boot from USB-stick. I can prepare USB-Sticks with Rufus or WinSetupfromUSB to be bootable. Problem 2: If I use Rufus, so the USB-Stick will not be bootable on the Acer. But I can "solve" problem2 by using WinSetupFromUSB (I tried several Versions, 1.0beta7 and 1.4). What I already did with WinSetupFromUSB: - Made a USB-Stick bootable with FAT32 file format - created a USB-Stick with WinXP-install-files; thereby the files were copied directly from a WinXP-install-CD, not from an ISO-file. Then it is principially possible to boot from this USB-Stick; I get first this screen http://www.winsetupfromusb.com/wp-content/uploads/2013/09/Ashampoo_Snap_2014.01.20_17h30m44s_001_QEMU.jpg and can select the WinXP Setup. The setup at the first starts fine, but after loading FAT file system I get - either a bluescreen with the 0x0000007B error (if I created the USB-Stick with WinSetupFromUSB1.0beta7) - or a blackscreen with blinking cursor in the top left of the screen. At http://www.winsetupfromusb.com/faq/ and http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html there are described some workarounds. I have tried some of them: 1.) I have already tried a modified ntdetect.com Ntdetect.7z, with no difference. 2.) I changed the BIOS setting "SATA MODE" from "AHCI Mode" tho "IDE Mode" and back, with no difference. 3.) I tried to select "Auto-detect and use F6 SATA/RAID/SCSI Driver" like described in http://www.winsetupfromusb.com/wp-content/uploads/2013/09, with no difference. 4.) I installed nLite on my (working) PC and tried to add following driver AHCI_Intel_8.8.0.1009_XPx86XPx64_A.zip, which also can be downloaded from Acer's website: http://global-download.acer.com/GDFiles/Driver/AHCI/AHCI_Intel_8.8.0.1009_XPx86XPx64_A.zip?acerid=633773721411807534&Step1=Notebook&Step2=Aspire&Step3=Aspire%203810T&OS=X01&LC=en&BC=Acer&SC=PA_6. But even 4.) had no effect :angrym: ! I get still the blue- or black-screen described above. Maybe I did something wrong? I think I have added the driver not properly into nLite. Could it have something to do with the fact that I would need "text mode drivers" (or similarly)? PS: I had to unpack the nLite ISO- file before creating the bootable USB-Stick with WinSetupFromUSB. PPS: Here is the *.ini-file created from nLite LETZTE SESSION.INI.

I just now tried to reproduce the output... With exactly the same result which I yet posted! Maybe we have different settings to execute batch files, or different versions of command.com?! Some modifications/notifications on my Win98 system which I can remember on the fly: I have here - Win98SE, version 4.10.2222A - actually KernelEx v4.5.2 installed - updated unicows.dll, version 1.1.3790.0 I saved it as echo.bat and started it by double-clicking on it. Following output: For some (for me unknown) reason the ampersand seems (here) not to produce an issue, contrary to your output. Could anybody other test one of the posted *.bat-files?

Principially the same error like if I try to print. Several (long) URLs are not passed(?) correctly to the command line, shorter "easier" URLs are passed correctly.It is not (only?) a problem with "special" characters, because I get the same error, if I manually produce a long URL *without* special characters, like C:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\test.txt, open this with firefox and then try to start my extension. It is not shown correctly in command line. I tried several versions with quotes; no success. It seems that the parameters must be completely inside the delimiters [].If I use following fire.bat: @ECHO OFFECHO http://www.google.de/search?hl=de&as_q=kommandozeilen+interpreter+win98&as_epq=127+zeichen&as_oq=&as_eq=&as_nlo=&as_nhi=&lr=&cr=&as_qdr=all&as_sitesearch=&as_occt=&safe=images&as_filetype=&as_rights=nicht+nach+Lizenz+gefiltertPAUSE then I get the following output: You can see that the (long!) example URL contents many special characters, which are shown correctly in the command line output. So in my opinion it is obviously the problem how to get the URL variable, "created" as String with the command gBrowser.currentURI.spec, to the command line. Maybe I should find another way to get the URL "outside" of firefox, e.g. into a temp *.txt file. But for that I would need also the command line...?! I already use this extension; "my" extension is actually based on it. Doesn't work. It will be printed the first page which firefox "sees" when accessing C:/temp.htm, and this is a blank page. Maybe it could work if firefox somehow "waits" some seconds before printing.

Yes, I mean the Win98SE command.com. Yes, the problem concerns too long URLs. I have the following code in one of my extension files: function progstart(exe, parameters) { if (!parameters || !parameters.length) parameters = []; var datei = Components.classes["@mozilla.org/file/local;1"] .createInstance(Components.interfaces.nsILocalFile); datei.initWithPath(exe); var proz = Components.classes["@mozilla.org/process/util;1"] .createInstance(Components.interfaces.nsIProcess); proz.init(datei); proz.run(false, parameters, parameters.length); } function FirefoxPrintA() { var a = "/k firefox -print " + gBrowser.currentURI.spec + " -printfile C:\zzw.png"; progstart('C:\\windows\\command.com', [a]); } function FirefoxPrintB() { var c = gBrowser.currentURI.spec; progstart('C:\\fire.bat', [c]); } I tried to use either function FirefoxPrintB or FirefoxPrintA. Both work fine while the URL got by gBrowser.currentURI.spec is not long. If I use FirefoxPrintB I additionally use a file called fire.bat with following content: D:\Programme\Mozill~2\firefox.exe -print "%1" -printfile C:\zzw.png The mentioned error message looks (in german) like this: If I change the content of fire.bat for test to D:\Programme\Mozill~2\firefox.exe -print "http://www.google.de/search?hl=de&as_q=dos+command.com+long+parameters&as_epq=&as_oq=&as_eq=&as_nlo=&as_nhi=&lr=&cr=&as_qdr=all&as_sitesearch=&as_occt=&safe=images&as_filetype=&as_rights=nicht+nach+Lizenz+gefiltert" -printfile C:\zzw.png so it works (with the long URL you can see). I can see in the "DOS-Box" after executing fire.bar that the whole URL is inserted. So I think it must be a problem while copying(?) the URL to "%1" in the first version of fire.bat. Possibly I should try to copy the URL directly into fire.bat, i.e. change fire.bat, while executing the firefox extension?!

While trying to write an extension for firefox 3 for Win98SE it's needed for me to include a certain *.bat-file (or directly execute command.com). I'm running into problems with long parameters/arguments to pass. I will explain the problem with a more simple example: I have a *.bat-file C:\notepadtest.bat with following content: c:\windows\notepad "%1" Furthermore I have a *.txt-file C:\testfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfile\testfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfile\test.txt with content test (the content of the *.txt-file plays no role). If I now try to execute C:\notepadtest.bat C:\testfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfile\testfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfile\test.txt, so it will not work! . (It will be shown a stupid error message instead of executing notepadtest.bat.) It has definitely to do with the (very) long parameter C:\testfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfile\testfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfiletestfile\test.txt. With shorter parameters the notepadtest.bat works correctly. But long parameters (concretely: URLs) would later be needed for the firefox extension. Is there any known way to pass long parameters into a *.bat-file? (Or alternatively to pass long parameters directly to c:\windows\command.com, using the /k commandline option?)

I tried Firefox 3.0.19 with Fireshot 0.76, and still got the error "There is no default printer currently selected". @farfigs11 I'm not sure how to add the mentioned KernelEx stubs 452 and 822. I modified the following line in core.ini: contents=K452stub,Kstub822,std,kexbases,kexbasen Furthermore I copied the files K452stub.dll, K452stub.ini, Kstub822.dll, Kstub822.ini into the KernelEx progrm folder. Was this correctly?

I'm not sure whether fireshot uses Firefox's intern printing engine. Fireshot seems to work like a graphic program, which takes a screenshot (like Alt+PrintScreen buttons pressed). Fireshot has own *.dll's: fsaddin.dll, Sss.dll, SSSLauncher.dll. Are there other known extensions for firefox, which work similarly? Maybe it could even be possible to create an own printing extension, but that could be very tricky... Yes. The error message"There is no default printer currently selected" seems to be sent by the file sss.dll, which belongs to fireshot: After that I get the following:

A long time ago I asked here whether somebody was able to print directly from Firefox 3.* under Win98SE with KernelEx. It seemed that nobody has/had a really satisfiying solution. Some days ago I found an extension called "fireshot" which could(?) be a possible solution, because it seems that it has its own printing engine(?). But its printing function doesn't work: If I try to print I get an error message: "There is no default printer currently selected." But I have a default printer! So the problem seems to be that fireshot can not find my printer. I added some registry hacks, but with no success. Is anybody able to print with Fireshot in Win98SE? Furthermore I found another extension which could maybe be helpful; called "Capture & print". But this does (generally) not work with Firefox3.*. Could it be possible to edit its source code to make it compatible with Firefox3?